| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Linux Only Beta Test |
| No member browsing this thread |
|
Thread Status: Locked Total posts in this thread: 177
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Progress indicators were definitely off on the first completed WU's but each have completed all 16 jobs normally, so far. The techs could claim that as a new beta feature. With WUs that end at some random time over 100%, users have no idea when to come back and try to obtain another beta WU! |
||
|
|
Randzo
Senior Cruncher Slovakia Joined: Jan 10, 2008 Post Count: 339 Status: Offline Project Badges: 
|
Yes is`t not a bug it`s a feature :-D :-D :-D
|
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
I've received 8 of these WU's. Two have been returned and validated; 6 are still running. They're fine with suspending and resuming. Estimated time to completion starts out too high, but the % complete ends up at 100%.
----------------------------------------They're running 3.5 - 4 hrs on the 2.53 GHz dual core. It looks as if the first one running on an Atom processor is about to finish after just over 10 hrs (both CPU times rather than wall clock).   |
||
|
|||
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges:
|
They're running 3.5 - 4 hrs on the 2.53 GHz dual core. It looks as if the first one running on an Atom processor is about to finish after just over 10 hrs (both CPU times rather than wall clock). Well, that's interesting. On the Atom, the task has continued to run even though the percent complete has stopped incrementing (at 100%). |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
One of my WUs (BETA_A.22.C17H10N2S3.8.3.set1d06) was stopped within job #15 after 12 hours by the time limit. The wingman was stopped after 12 minutes within job #2 with the mssage
Application exited with RC = 0x100 [10:07:39] Finished Job #2 [10:07:39] Starting job 3,CPU time has been restored to 616.423288. [10:07:39] Skipping Job #3 ... [10:07:39] Starting job 15,CPU time has been restored to 616.423288. [10:07:39] Skipping Job #15 called boinc_finish Both jobs became valid. It's a pity that one task is stopped by an error so early while the other continues. Guess in production only the first two jobs can be validated while all others will be redone by the next WU. A waste of nearly 12 hours work for 13 jobs... Or did I get something wrong? |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
mweisensee,
Actually your result will be the one sent the researcher if you got further in the run. Only if the other checks on the work unit pass as well. But if yours is valid and gets further, your result is the one marked as the answer. -Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ah, that's fine. I hope those other checks are really reliable enough to ensure single redundancy for those additionally computed tasks.
Anyway, thanks for the quick response! :-) |
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges:
|
I've received 8 of these WU's. Two have been returned and validated; 6 are still running. They're fine with suspending and resuming. Estimated time to completion starts out too high, but the % complete ends up at 100%. They're running 3.5 - 4 hrs on the 2.53 GHz dual core. It looks as if the first one running on an Atom processor is about to finish after just over 10 hrs (both CPU times rather than wall clock). I can now report that the 4 betas on the Atom machine came back up and restarted after the computer, and Boinc with it, were taken down instantaneously by a power failure. I guess that's good news for the beta test. (I practically went into withdrawal when the power was off for 5 hours and I couldn't crunch...)  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I guess that's good news for the beta test. (I practically went into withdrawal when the power was off for 5 hours and I couldn't crunch...) Just remember ---- "Crunching is not an Addiction... It's an Obsession"  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My laptop started to crunch two Betas yesterday evening, and when I went to bed they showed approx 30 % completed (don't remember for how long they have been running by then). For whatever reason my laptop switched itself off tonight and when I restarted it, both tasks restarted at around 0.2% - and now, after 1 hour of crunching, they are at 55 %... Betas on this laptop usually run for 4 to 5 hours.
BETA_ A.23.C15H7N5S3.2.2.set1d06_ 0-- BETA_ A.23.C16H10N4S2Si.3.2.set1d06_ 1-- Is this percentage calculation due to the Beta status or is it a "feature"? |
||
|
|
|