Anybody know what's going on here?! I don't really mind though...

EDIT: Notice the timestamp down the bottom... 5 December...

---

- Luke.

Anybody know what's going on here?! I don't really mind though...

EDIT: Notice the timestamp down the bottom... 5 December...

Kind of looks like your pc clock for whatever reason was set to a future date around the 22nd and then was corrected.

---

Anybody know what's going on here?! I don't really mind though...

EDIT: Notice the timestamp down the bottom... 5 December...

Kind of looks like your pc clock for whatever reason was set to a future date around the 22nd and then was corrected.

Now that you tell me, I did change my clock yesterday to the 6th and then reverted it, so that really screws with BOINC does it? I wouldn't of guessed that...

Case closed.

---

- Luke.

Anybody know what's going on here?! I don't really mind though...

EDIT: Notice the timestamp down the bottom... 5 December...

Kind of looks like your pc clock for whatever reason was set to a future date around the 22nd and then was corrected.

Now that you tell me, I did change my clock yesterday to the 6th and then reverted it, so that really screws with BOINC does it? I wouldn't of guessed that...

Case closed.

I would imagine it's probably not a good thing to do in general when it comes to Boinc, since the task do check points and changing the time I would think could potentially cause tasks to restart at a previous check point or even cause errors.

---

This problem won't affect actual computation or checkpointing, and shouldn't cause any errors. However, it will cause unexpected side effects, and should be avoided.

While the clock is set in the future
You may get warning messages about tasks not finishing in time, and processing may switch to 'High Priority' ('Earliest Deadline First') mode. Some people may even be induced to abort perfectly good work, on the basis of a BOINC assertion that it won't be finished in time.

After the clock is set back to the correct time
BOINC will attempt to run CPU benchmarks, and never finish them - resulting in no work being done at all. This happens once only, and clears itself the next time BOINC is restarted - I guess Luke has passed this problem already.

BOINC's estimate of how much work it can do will be screwed up, and it will maintain a much lower cache utilisation than usual. This will continue until the real clock catches up with the latest 'future time' reached during the episode - 6 December in this case.

All of this is documented in Trac ticket [trac]#588[/trac]. Ignore the spam comment at the bottom.

This problem won't affect actual computation or checkpointing, and shouldn't cause any errors. However, it will cause unexpected side effects, and should be avoided.

While the clock is set in the future
You may get warning messages about tasks not finishing in time, and processing may switch to 'High Priority' ('Earliest Deadline First') mode. Some people may even be induced to abort perfectly good work, on the basis of a BOINC assertion that it won't be finished in time.

After the clock is set back to the correct time
BOINC will attempt to run CPU benchmarks, and never finish them - resulting in no work being done at all. This happens once only, and clears itself the next time BOINC is restarted - I guess Luke has passed this problem already.

BOINC's estimate of how much work it can do will be screwed up, and it will maintain a much lower cache utilisation than usual. This will continue until the real clock catches up with the latest 'future time' reached during the episode - 6 December in this case.

All of this is documented in Trac ticket [trac]#588[/trac]. Ignore the spam comment at the bottom.

Thanks Richard, good to know..appreciate it.

---