| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Short Schedule [RESOLVED] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The following WU has an extremely tight timeframe. I am going to let it run and let the Techs worry about it after.
----------------------------------------BETA_ E000370_ 388A_ 001e95186_ 2-- Expedition In Progress 04/12/08 10:29:13 04/12/08 20:05:13 0.00 0.0 / 0.0 [Edit 1 times, last edit by Former Member at Dec 15, 2008 7:19:59 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
astrolab, this is discussed in the existing Beta threads for the current tests. Let it run.
----------------------------------------cheers
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1411 Status: Offline Project Badges: 
|
Another very short deadline (considering my oldie laptop: AMD Sempron 2800+ - 1.6GHz).
All times UTC+1 4-12-2008 18:15:04 Downloaded 4-12-2008 18:15:05 Starting BETA_E000370_118A_001e8z180_2 5-12-2008 03:49:50 Deadline 4-12-2008 19:25:00 4% Done in 1h8m4s So estimated total runtime 28 h 21m 40s. I don't bother credits, however I wanna my Beta badge  some day in the next ten years. |
||
|
|
Ian_UK
Senior Cruncher England Joined: Oct 15, 2006 Post Count: 153 Status: Offline Project Badges: 
|
Last post on same issue was probably missed.
----------------------------------------BETA_ E000370_ 371A_ 001e95169 now has been sent out 5 times, as 3rd & 4th people were all been given deadlines that were unreasonable and thus another unit got resent (3 people are now crunching for probably one result - Good luck to the winner!). One person was expected to crunch the same unit that took another over 21hours to do in 8 hours. Hopefully not too much effort has been wasted crunching these units. Can someone look at these deadlines to stop our efforts being wasted (and yet another unit going out again??????). |
|||
|
||||
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges: 
|
Last post on same issue was probably missed. ... Hopefully not too much effort has been wasted crunching these units. Can someone look at these deadlines to stop our efforts being wasted (and yet another unit going out again??????). Other threads on the same issue have been certainly missed...  Once again, deadlines are not important during Beta tests. They are intentionally set short to force Boinc to prioritize those WUs. Also, as uplinger says in another thread, testing behavior in all situations including too late is part of the test. All results are useful including late ones, and WUs which reached completion are credited normally, whatever their final status. Bottom line 1: nothing is wasted, except WUs that you might have aborted too fast. Bottom line 2: remember that participation to beta programs is optional, so if that disturbs you too much nobody will be shocked if you do not participate. Cheers. Jean. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The following WU has an extremely tight timeframe. I am going to let it run and let the Techs worry about it after. BETA_ E000370_ 388A_ 001e95186_ 2-- Expedition In Progress 04/12/08 10:29:13 04/12/08 20:05:13 0.00 0.0 / 0.0 finished BETA_ E000370_ 388A_ 001e95186_ 2-- Expedition Valid 04/12/08 10:29:13 05/12/08 13:17:06 21.39 267.2 / 261.2 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
the system gave me only 9.5 hours to crunch this Beta WU.
BETA_ E000370_ 210A_ 001e91184_ 4-- No Reply 12/5/08 02:27:01 12/5/08 12:03:01 0.00 0.0 / 0.0 It is still crunching, and is at 38.8% with just over 10 hours run so far. I have beta WU's running on all 5 of my machines right now. They all appear to be running with time frames that are too short to complete, and will end up with a no reply status. Is the 9.5 hour deadline a system glitch? I thought the short time frame for the Beta's was 24 hours, not 9.5. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
the system gave me only 9.5 hours to crunch this Beta WU. BETA_ E000370_ 210A_ 001e91184_ 4-- No Reply 12/5/08 02:27:01 12/5/08 12:03:01 0.00 0.0 / 0.0 It is still crunching, and is at 38.8% with just over 10 hours run so far. I have beta WU's running on all 5 of my machines right now. They all appear to be running with time frames that are too short to complete, and will end up with a no reply status. Is the 9.5 hour deadline a system glitch? I thought the short time frame for the Beta's was 24 hours, not 9.5. OK, discussions about this issue are on-going in two other threads. No need to reply to me here. |
||
|
|
mikefinn
Cruncher USA Joined: Apr 27, 2007 Post Count: 43 Status: Offline Project Badges: 
|
Once again, deadlines are not important during Beta tests. They are intentionally set short to force Boinc to prioritize those WUs. Also, as uplinger says in another thread, testing behavior in all situations including too late is part of the test. All results are useful including late ones, and WUs which reached completion are credited normally, whatever their final status. Cheers. Jean. Thank you for posting this. I am new to beta testing. Because I read your post, I was saved from erroneously aborting a beta work unit. I have one of those high priority WU. When I went to bed, it had about 5 hours to go on a deadline that was 6 hours away, so I left the computer on instead of my usual routine of shutting down for the night. I fully expected I would wake up 7 hours later and find it completed. Well, when I did get up, I found that it still had 2 hours 30 minutes of time remaining to run and it also looked like the total run time had been recalculated and it was now higher. I also had a message that the WU has 0.10 days overdue and I should consider aborting it. I'm glad I read your post first and didn't abort. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Once again, deadlines are not important during Beta tests. They are intentionally set short to force Boinc to prioritize those WUs. Also, as uplinger says in another thread, testing behavior in all situations including too late is part of the test. All results are useful including late ones, and WUs which reached completion are credited normally, whatever their final status. Cheers. Jean. Thank you for posting this. I am new to beta testing. Because I read your post, I was saved from erroneously aborting a beta work unit. I have one of those high priority WU. When I went to bed, it had about 5 hours to go on a deadline that was 6 hours away, so I left the computer on instead of my usual routine of shutting down for the night. I fully expected I would wake up 7 hours later and find it completed. Well, when I did get up, I found that it still had 2 hours 30 minutes of time remaining to run and it also looked like the total run time had been recalculated and it was now higher. I also had a message that the WU has 0.10 days overdue and I should consider aborting it. I'm glad I read your post first and didn't abort. It might be beneficial, in the future, to post disclaimers when announcing a new Beta. Because of past Beta projects I crunched for, I Knew that I should let the WU completely crunch. I think some are quick to abort the WU because they feel they will be crunching for nothing. They feel this because they realize that their computer will not complete the crunching of the WU by the set deadline. If I remember correctly, these same issues occurred when AC@H was Beta tested. The announcement of the new Beta could read like this (the first part is from Nelsoc's actual post and some is from a post by Uplinger): "We are going to begin shortly a slightly larger Beta Test for Windows for the application for an upcoming project. Please let the work unit completely crunch. Deadlines are not important during Beta tests. They are intentionally set short to force Boinc to prioritize those WUs. Also, testing behavior in all situations including too late is part of the test. All results are useful including late ones, and WUs which reached completion are credited normally, whatever their final status." On another note, I thought they were set to a short time frame of 24 hours. Some of the WU's went out last night with a turn around time of 9.5 hours. My quickest 2 machines are on line to complete 4 Beta WU's with an estimated completion time of 16 to 24 hours. [Edit 1 times, last edit by Former Member at Dec 5, 2008 3:59:33 PM] |
||
|
|
|