I got a 'Validate Error' on one of my WUs:

http://setiathome.berkeley.edu/result.php?resultid=1209407979

What happens to this? Is there any further attempt to validate the WU?

---

I'm not 100% sure, but I see the flop counter is slightly different for the two reported tasks. I can't remember if that makes a significant difference with the validator, or if that only checks for signals and the strengths of said signals.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I just now noticed one that looks similar:

Task 1200507720

If anything, I would have thought "Completed, validation inconclusive" would be more appropriate rather than "Validate error" on both TerryG's and mine. It also may be notable that both were returned within about 5 minutes of each other.

Problem with the validator just as it was coming up ??

Edit to add TerryG's Workunit link

I just now noticed one that looks similar:

Task 1200507720

If anything, I would have thought "Completed, validation inconclusive" would be more appropriate rather than "Validate error" on both TerryG's and mine. It also may be notable that both were returned within about 5 minutes of each other.

Problem with the validator just as it was coming up ??

Edit to add TerryG's Workunit link

I hope it was a transient condition.

Although the new layout of workunit pages no longer has an "explain" button for the Status column, the "Validate error" indication means the same as it previously did in the Outcome column. The Validator was not able to find the uploaded result file. It cannot go to the inconclusive state because BOINC will not look for the file again; it's considered a permanent error.

I did check the times in the threads about hosts suddenly acting as if they were attached to SETI Beta, but that seems to have ended ~45 minutes before these validate errors.

In addition to the possibility the uploaded file actually got lost (or was saved the wrong place), the Validator has to do a database query before it knows where to look for the file. With the database acting up that seems a likely cause.

                                                                Joe

I hope it was a transient condition.

                                                                Joe

My hope as well. Thanks as usual Joe.