| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: New Beta Test - February 25, 2016 [ Issues Thread ] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 91
|
|
| Author |
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: 
|
I have a task that is at 227% complete after 10.5 hours. I have suspended it for now. It is not a resend. What should I do with it? You could restart the computer to clear out any problems. I had a WU stuck at 100%. Rebooted the PC, and the WU reported as finished after the reboot. Patrick  |
||
|
|
ALAIN_13013
Advanced Cruncher France Joined: Nov 28, 2006 Post Count: 83 Status: Offline Project Badges: 
|
trop tard pour une unité de 18h traitée en moins de 24 heures
----------------------------------------too late for a WU of 18 hours run within 24 hours https://secure.worldcommunitygrid.org/ms/devi....do?workunitId=1636434126  |
|||
|
||||
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
From the Italian 'Troppo tarde' ... the French should only use French words, at least, that's what your minister of culture wants ;>)
----------------------------------------Why getting annoyed I do not know because the next copy will also need that much time, thus by the time yours is finished it will still be returned sooner then the No Reply. Then the servers will send a message to the machine with the later copy to not start computing. If it does and finishes, it will still be credited. And, you'll have to give your password for us to see the detail of your work unit on -your- result status page i.e. you need to copy / paste the detail in a reply for us to see. In short: posting links to work units does not work. [Edit 1 times, last edit by SekeRob* at Mar 4, 2016 8:20:53 AM] |
||
|
|
yoro42
Ace Cruncher United States Joined: Feb 19, 2011 Post Count: 8978 Status: Offline Project Badges: 
|
Part 1: (Past)
----------------------------------------BETA_ E236296_ 51_ S.318.C34H26N8O4.JROMKOQQZBTQJK-UHFFFAOYSA-N.9_ s1_ 14_ 3-- Coltrane Too Late 03/04/16 04:04:10 PM 03/05/16 02:28:46 AM 10.15 / 10.38 285.7 / 0.0 The above WU arrived around 4 PM on March 4th and was still in a Ready to start status yesterday Morning. So I suspended all other WUs that were Ready to start. After awhile it became obvious it would not make the then listed March 5th, 6 PM Deadline which has not yet arrived. So I suspended all but 5 or 6 WUs out of 12 processors to favor the only Beta running. When I checked later The Beta WU's progress was at 48% and would make the deadline. When I checked back later to find the WU was ended as To Late. Part 2: (Present) The following Beta WU looks like it could have the same demise BETA_ E236296_ 650_ S.318.C35H26N6O1S2.VKKXLMXWYYQJIZ-UHFFFAOYSA-N.4_ s1_ 14_ 2-- Ella In Progress 3/5/16 18:46:54 3/7/16 04:22:53 0.00 / 0.00 0.0Â /Â 0.0 World Community Grid 7.00 beta11 BETA_E236296_650_S.318.C35H26N6O1S2.VKKXLMXWYYQJIZ-UHFFFAOYSA-N.4_s1_14_2 03:30:39 (03:27:58) 3/5/2016 11:47:00 AM 19.257 01d,03:34:20 3/6/2016 9:22:53 PM Running High P. Ella_ 132.62 MB 261.13 MB [0] 03:27:58 98.22 Update: World Community Grid 7.00 beta11 BETA_E236296_650_S.318.C35H26N6O1S2.VKKXLMXWYYQJIZ-UHFFFAOYSA-N.4_s1_14_2 04:35:32 (04:31:50) 3/5/2016 11:47:00 AM 25.170 01d,02:08:27 3/6/2016 9:22:53 PM Running Ella_ 135.43 MB 269.62 MB [0] 04:31:50 98.39 All other WU on the system have been suspended and the WU shows 25% progress and 1 day 2 hours 4 minutes Time Left. Progress and Time Left seem to be at odds with each other.  |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Just let them run... the next copy could not possibly finish before yours, provided you started them immediately [unless Blue Gene gets involved]. If tasks get within 24 hours of deadline or the deadline is less than twice the remaining time computing time, they will be processed in high priority. If you stop work fetch and set the buffer to 2 days, they'll be rushed to the end without manual intervention, v7 at least. (Just some of the auto-exception rules to optimize client scheduling).
----------------------------------------Sadly the 35% deadline rule for repairs is a BOINC wide rule, speak WCG... so applies to beta too, hence why we get those silly deadlines on long running beta tasks. They [techs] can compute appropriate deadlines backwards... if they know the runtimes are 30 hours, then 30 hours / .35 = 85 hours i.e. a 96 hour standard deadline is 33.6 hours for repairs. That's calling it close. Since habitually many beta's are launched on Friday, the bulk is likely to launch on 24/24 machines, i.e. should work to get most all originals back on Monday. The toruble though is, on Tuesday the repairs start landing on part-time machines too. They'd be in trouble. Maybe the Beta program could be made more qualified on the Beta-opt-in page: "Since deadlines on beta tasks are short, it may be necessary to keep the participating devices running all day as work assignments might need long hours to compute". (From the dumb and dumber department) [Edit 1 times, last edit by SekeRob* at Mar 6, 2016 8:11:09 AM] |
||
|
|
rbotterb
Senior Cruncher United States Joined: Jul 21, 2005 Post Count: 401 Status: Offline Project Badges: 
|
One option SekeRob would be to run Beta runs starting on Wednesdays or Thursdays instead of Fridays. The 24/24 machines will be there to finish much of the work by early weekend, and then the same machines would be more likely to catch the reruns into the weekends to finish them up quickly as well. You might need to try this a time or two to see if statistically it works out better for your beta teams, but I suspect it would give you a better turnaround on your work and have fewer Beta WUs ending up on part-time machines.
|
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Seconding that idea, also becauuuuse, then a tech can intervene when it turns bad like last on CEP2 test during the weekend. Nobody there to handle the maximize use issue.
----------------------------------------[Edit 1 times, last edit by SekeRob* at Mar 6, 2016 1:19:25 PM] |
||
|
|
yoro42
Ace Cruncher United States Joined: Feb 19, 2011 Post Count: 8978 Status: Offline Project Badges:
|
Part 3: (Update of Recent Past) After releasing all other WUs and allowing the betas to run both completed with Valid status in less than the estimated 1d 3+hrs: BETA_ E236296_ 645_ S.318.C37H26N2O1S3.MRNLZRMXKILQMN-UHFFFAOYSA-N.14_ s1_ 14_ 2-- Ella Valid 3/5/16 18:46:54 3/6/16 08:19:39 9.77 / 9.87 299.0 / 306.3 BETA_ E236296_ 650_ S.318.C35H26N6O1S2.VKKXLMXWYYQJIZ-UHFFFAOYSA-N.4_ s1_ 14_ 2-- Ella Valid 3/5/16 18:46:54 3/6/16 03:41:35 8.77 / 8.88 269.1 / 377.5 Rob & rbotterb, Thanks for the three preceding post. |
||
|
|
vepaul
Senior Cruncher Belgium Joined: Nov 17, 2004 Post Count: 261 Status: Offline Project Badges:
|
Here are my results:
BETA_ E236296_ 482_ S.314.C35F1H22N7O1S1.NJABVAFRKGUYRB-UHFFFAOYSA-N.6_ s1_ 14_ 2-- paul-HP2 Non concluant 5/03/16 18:19:43 6/03/16 12:10:18 15,32 / 15,47 455,1 / 0,0 BETA_ E236297_ 359_ S.314.C35H21N5O6.MZBKBPYYGCABTL-UHFFFAOYSA-N.18_ s1_ 14_ 0-- paul-HP2 Valide 1/03/16 19:47:04 2/03/16 08:13:59 9,87 / 9,98 293,6 / 331,7 BETA_ E236293_ 250_ S.320.C41H29N3O1S1.DDFHVWITZPPDEG-UHFFFAOYSA-N.1_ s1_ 14_ 3-- Bureau2-HP Erreur 1/03/16 16:15:29 2/03/16 07:55:15 13,20 / 13,42 368,9 / 368,9 vep  |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1271 Status: Offline Project Badges:
|
Please keep this thread on topic. There is a CEP 2 beta thread. This thread is for the new beta test Thanks
----------------------------------------I am looking forward to hearing more news about and how the 1st beta went for the new project. At lunchtime on 3/7/16 there were a total of 179 results returned. Unfortunately I do not know what the share is between the 2 projects  |
||
|
|
|