WU Received With 7 Hrs To Deadline

Message boards : Number crunching : WU Received With 7 Hrs To Deadline

Author	Message
cov_route Send message Joined: 13 Sep 12 Posts: 86 Credit: 1,735,155 RAC: 2,906	Message 1325933 - Posted: 9 Jan 2013, 3:13:17 UTC
	Well, isn't this random... http://setiathome.berkeley.edu/workunit.php?wuid=1139358116
	ID: 1325933 ·

bill Send message Joined: 16 Jun 99 Posts: 604 Credit: 14,542,317 RAC: 25,495	Message 1325938 - Posted: 9 Jan 2013, 3:28:47 UTC - in response to Message 1325933.
	Happens to everybody.
	ID: 1325938 ·

BilBg Send message Joined: 27 May 07 Posts: 2095 Credit: 3,274,787 RAC: 7,846	Message 1326006 - Posted: 9 Jan 2013, 8:47:18 UTC - in response to Message 1325933.
	Probably expired because the 2 original tasks were 'Completed and validated' before your task started (server sends 'delete request' to your BOINC before your task is started) (the original Deadline was for sure Not 7 h) ____________ - ALF - "Find out what you don't do well ..... then don't do it!" :)
	ID: 1326006 ·

Josef W. Segur Volunteer developer Volunteer tester Send message Joined: 30 Oct 99 Posts: 3969 Credit: 937,921 RAC: 170	Message 1326113 - Posted: 9 Jan 2013, 17:36:50 UTC - in response to Message 1326006.
	Probably expired because the 2 original tasks were 'Completed and validated' before your task started (server sends 'delete request' to your BOINC before your task is started) (the original Deadline was for sure Not 7 h) No, that would show as aborted rather than timed out. Almost certainly the task was ghosted originally - the host never actually knew it had been "sent" so never downloaded it. The WU was already resolved when the request 7 hours later was being checked, so the "resend lost work" logic expired it then. A 7 hour backoff before the next request is certainly possible, or enough ghosted tasks that it took several requests before reaching that part of the lost work. Joe
	ID: 1326113 ·

Message boards : Number crunching : WU Received With 7 Hrs To Deadline