Incorrect backoff times in 1.32 project properties

Started by Fred E., July 24, 2012, 01:04:05 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Fred E.

Minor glitch, probably the same as Mark J observed for v1.30 - the project properties shows garbage when backoff times are in effect:  Example:

BoincTask 1.32:

CPU backoff time                         15545d,10:51:21
Backoff Interval                                      00:20:00
NVIDIA backoff time                     15545d,10:33:21
Backoff Interval                                      00:20:00

BOINC 7.0.28 for Windows 32 bit:

CPU work fetch deferred for                      00:14:26
CPU work fetch deferral interval                00:20:00
NVIDIA GPU work fetch deferred for           00:01:20
CPU work fetch deferral interval                00:20:00

fred

Quote from: Fred E. on July 24, 2012, 01:04:05 PM
Minor glitch, probably the same as Mark J observed for v1.30 - the project properties shows garbage when backoff times are in effect:  Example:

BoincTask 1.32:
Try the beta version http://www.efmer.eu/boinc/boinc_tasks/download_beta.html, if the problem is still there, report it here.
The beta is stable, even more so than the 1.32.  8)

Fred E.


fred


Fred E.

QuoteDid it solve things?

:( No, still the same  - no work from SETI for 15k days!  Guess I irritated someone. 
Not a big deal, just letting you know in case you do some work in the area.

Will stay with this version.   

BobCat13

Running BT 1.37 on Localhost

Localhost (WinXP SP3 32-bit, ver. 6.12.43)

Project Orbit@home
CPU backoff time   7-25-2012 6:42:04 AM
Backoff Interval   24:00:00
   

Remote Linux (Lubuntu 11.10, ver. 7.0.27)

Project Rioja Science
CPU backoff time   373105:27:39
Backoff Interval   00:10:00

The 373105 is hours since January 1, 1970, in case that helps.  Fred E.'s 15545 is the number of days since January 1, 1970.