Result was reported too late to validate!?
Anonymous
23 May 2006 16:59:45 UTC
Topic 13334
(moderation:
Quote:
I've gotten three results given 0 credit because the "result was reported too late to validate", even though the due date isn't till June...
I think something is messed up...
You're absolutely right: something is messed up. This is a bug in the back-end BOINC server components, which I think was introduced on March 11th when David Anderson made some changes to the code. It has affected a couple of hundred results on Einstein@Home.
I've spent about 12 hours trying to track it down with no success yet, though I have inserted a bunch of debugging code into the scheduler which should make it easier to track down.
David Anderson checked and he has the same bug in SETI@Home, affecting about six hundred results. He's also looking to see if he can figure out what's wrong.
I am sure we can track this down and fix it. Thank you very much for pointing this out -- it seems to be the first scheduler/back-end bug that has shown up now in almost three months.
(By the way, it would be helpful to David and me to get a copy of your sched_request_einstein.phys.uwm.edu.xml file, and the corresponding sched_reply. Please don't post them here because they have your authenticator in them. Could you email them to me?)
Bruce
Result was reported too late to validate!?
)
Problem should now be fixed.
Affected machine need to contact the scheduler twice before they start acting 'normal' again. You should cancel/abort any workunits currently in progress on the machine, as they have already been marked as 'errors' in the database. So CPU time spent on those in-progess results is wasted. Look at the 'my results' web page to see if that work has already been marked as 'client error'.
If your machine has this problem, your machine's sched_reply_einstein.phys.uwm.edu.xml file will contain
NUMBER
which has other text before it on the same line. This was caused by a bug in code used by Grid Republic.
Cheers,
Bruce