World Community Grid - View Thread - [RESOLVED] No tasks running

The 15th was right per your log... BOINC does not care about time so much, a whole lot more about date. If your system were on the 15th when fetching new work, then the date set back 9 days or more, the client would think it could not make the deadline, switch to high priority processing, or tell to abort the tasks as they have expired.

Emphasis mine.

That is a 'dangerous' proposition to make. A date, hours, minutes, and seconds are all expressions of "time". Perhaps you may want to be more precise in your choice of words. Did you mean clock-time when using the word "time"? If so, did you mean that the maximum time-resolution that BOINC can resolve is ±23hrs59min59sec so that BOINC can't see the difference between, say, 0700 and 1900 of a given date?

If we are agreed on the above, then there would be no need for WCG to specify time in date + (hours, minutes, and seconds) in BOINC and the Results Status webpage -- be it for referring to Send-time, Time-due, Return-time, deadline -- in as much as BOINC can't resolve hours, minutes, and seconds anyway.

P.S.
I'm glad that the OP's issue was resolved, but as far as time is concerned, it was the synch via NTP that provided the exact time to the second that did the trick, and that BOINC has to resolve time to the second referenced from a given time zone if BOINC is do its work correctly and accurately. A difference of 1 second spells the difference between the end of a day, and the start of another day.
;
;edit1_2012.06.17Su.1936.utc
;edit2_2012.06.17Su.1940.utc
; - spell check
;