Boinc 5.10.45 win XP pro SP2+ 32bit AMD 2600+ 1.5G RAM

Task shows computational error and is now working on next task in list.
Re-boot and task list now just shows task completed.

(force)Update project
project site: my tasks shows Done:error

BUG or WAD

I "know" I have a intermittent HW problem (memory bus) that may have caused the error.
Since the error was logged to BOINC manager, I assumed it was now the managers job to keep the correct status SHOWING on the User Interface task list through reboots.

Rosetta (the site) acknowledged the error that the task originally showed.
So how does BOINC manager track result "status" before the result is returned?
WAD?

Boinc 5.10.45 win XP pro SP2+ 32bit AMD 2600+ 1.5G RAM

Task shows computational error and is now working on next task in list.
Re-boot and task list now just shows task completed.

(force)Update project
project site: my tasks shows Done:error

BUG or WAD

No, it's not a bug, just imprecise feedback to user. It would be less confusing if the task list said something like "task completed but with computation error" after a reboot. That would be more congruent with what task list says prior to re-boot. It's not a biggee in my books but others may feel differently.

It would be nice to have correct status in this case rather than let my computer continue to crunch out garbage since my task list has many tasks to do before the automatic return kicks in.

Anway, I submitted Trac ticket #621 for this issue.

I think the way the WU outcome is reported on the Tasks page of a project's website also changes the same way:

Client error	Compute error

if the task is reported before a BOINC restart, and

Client error	Done

if it's reported afterwards. That could be fixed at the same time.

I think you may be right but I'm not about to induce a computation error in any of the tasks I have running at the moment to verify (too much CPU time invested). Are you certain? Can anyone else verify?

I have a slightly unstable new build which has thrown up a few errors recently.

If I see another one, I'll do the restart and see what changes.

Of course, by typing that I'm trying to invoke Murphy - when you want an error, everything runs smoothly. But does this count as a double-Murphy?

Anway, I submitted Trac ticket #621 for this issue.

Thanks.
I have been using BOINC for a bunch of years now (Seti,Rosetta and Simap). This is the first time I get to contribute a bug reporting that can do nothing but make BOINC better in the end.

Thanks to the BOINC staff (and volunteers) for their effort

I think the way the WU outcome is reported on the Tasks page of a project's website also changes the same way:

Client error	Compute error

if the task is reported before a BOINC restart, and

Client error	Done

if it's reported afterwards.

I think you may be right but I'm not about to induce a computation error in any of the tasks I have running at the moment to verify (too much CPU time invested). Are you certain? Can anyone else verify?

I'm still not certain, but I can supply some corroborative evidence.

SETI Beta WU 1105766 is a normal 'surplus to requirements' cancellation.

SETI Beta WU 1106057 is the same thing, but with a local BOINC restart between the server issuing the cancellation instruction, and the client reporting that it has received it. We get the "Done" client state, instead of the proper one.