| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Delay to send Beta Units too short |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 18
|
|
| Author |
|
|
TBirdTheYuri
Advanced Cruncher France Joined: Mar 5, 2006 Post Count: 115 Status: Offline Project Badges: 
|
I have received today a Beta unit but even with my Core 2 Quad full time dedicaced to this project, time was too short and my unit was listed as "too late" after 10 hours of calculation.
It would be good to extend some deadlines for these units, otherwise it will never happen to have conclusive results.  https://secure.worldcommunitygrid.org/ms/devi...us.do?workunitId=64513616 |
|||
|
||||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Can't see your details, no one can except the techs and the others in a quorum and . Was the deadline that short, as the original was I thought 4 days and make-up/repair jobs get 33% of that. Occasionally jobs get marked *too late* when the *no reply* comes back after all, but that has in past been corrected by running revalidation. Anyway, it's possible the validation run was not done yet as the few Beta jobs I got are quorum complete, but all sitting in *Pending Validation*
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Perhaps your queue is too long, TBirdTheYuri. Normally, the scheduler will refuse to send a task if it calculates that it won't finish in time. However, with a long queue, the estimates are less reliable.
Remember, we can't see the task information using the link you provided. |
||
|
|
TBirdTheYuri
Advanced Cruncher France Joined: Mar 5, 2006 Post Count: 115 Status: Offline Project Badges:
|
The length of the tail has no influence here, as the unit arrived in priority and immediately calculated by the machine. It simply came with a deadline a few hours shorter than the time required to perform the calculation (and still is my Core 2 Quad, which has received, the faster my machine)
Unit received yesterday at 2h30 AM with a deadline at 4h30 the same day (approximately). Calculation start immediately but the time required for terminate this unit by my Q9450 is up to 10 hours. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
My couple of Beta jobs are still sitting in 'Pending Validation'. I guess thus the validition run has not been done yet or there is a bug in the clearing process. Wait and see if the condition changes is all I have as advice atm.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I seem to be having a similar issue with dealines, a beta WU
BETA_ CMD2_ 0001-1RKC_ A.clustersOccur-1YGR_ B.clustersOccur_ 0_ 3-- arrived on the 15th with an expected return of 16/04/09 22:21:28, that has clearly passed regardless of which time zone you are in and the result is listed as too late in the results page. Currently the unit has been running for 13 hours to get to 49%, should I just allow this WU to complete or abort it? |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Beta's are much preferred to just let run, even if late. Normally jobs due that short are started immediately by BOINC. The client will interrupt anything and put the rush job in High Priority but if there are more in cache with even earlier deadlines, nothing will put them in front.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I suspected that the betas would better off completed but its nice to know, thank you for the prompt answer Sekerob
----------------------------------------[Edit 1 times, last edit by Former Member at Apr 17, 2009 10:04:09 AM] |
||
|
|
roundup
Veteran Cruncher Switzerland Joined: Jul 25, 2006 Post Count: 843 Status: Offline Project Badges: 
|
... full time dedicaced to this project, time was too short and my unit was listed as "too late" after 10 hours of calculation. It would be good to extend some deadlines for these units, otherwise it will never happen to have conclusive results. Same problem here with following WU: BETA_ CMD2_ 0001-1K04_ A.clustersOccur-2DDF_ A.clustersOccur_ 0_ 4-- 13.27 crunching hrs Result status: Too late |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
Unit received yesterday at 2h30 AM with a deadline at 4h30 the same day (approximately). The problem really seems to be there. TBirdTheYuri, if this WU is still in your Results Status page that could be interesting to paste its quorum details here since nobody else than you and the techs can use the link you have provided in your opening post. Also tell us which copy was yours in case it is not obvious from the times. Assuming that the routine which computes the deadlines is the same in all cases I cannot figure out on which original deadline yours has been based? Thanks in advance. Jean. |
||
|
|
|