| 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 Starting 2011/07/22 |
| No member browsing this thread |
|
Thread Status: Locked Total posts in this thread: 296
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The first test I did not look in, just let it run. Now checking:
----------------------------------------RAM 120MB Commit and Peak workset. Progress odd: Elapsed runs per wallclock, the CPU time freezes, slowly reducing the observed efficiency as shown in BOINCTasks, then the CPU time leaps forward and efficiency jumps to near 99%. Also the time since last checkpoint time freezes at about 13-15 seconds, then resets at next checkpoint, races to 13-15 seconds, then freezes again et cetera et cetera. Not good for the stressed and easily nerved :P --//-- edit: Should have qualified more.... the above is what's seen on Linux. On W7-32 the inter-checkpoint progress is normal upon verifying. [Edit 1 times, last edit by Former Member at Jul 27, 2011 4:00:23 PM] |
||
|
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges: 
|
They're still coming but not for me
---------------------------------------- 27/07/2011 16:48:11 World Community Grid Message from server: (there was work but it was committed to other platforms)  Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
coolstream,
Until now, you'd not get Beta ''out of work or other platform available'' messages. Have you got Intermittent work selections... DDDT2 maybe or HCMD2? They'd tell such. --//-- |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Uplinger, my computer managed to pick up two repair jobs - both of which had earlier copies fail with errors. The two WU's I picked up were; BETA_ BETA_ ampc_ 0000000_ 0259_ 3 BETA_ BETA_ ampc_ 0000000_ 0530_ 5 The 0259 had copies _0 & _1 abort with "Maximum elapsed time exceeded" (I can post the entire message logs if you require), whilst the 0530 had two copies (_0 & _1) also abort with this condition, whilst copies _2 & _3 aborted with "exit code 239 (0xef)". In both instances, the copies my compuer has, appear to be running successfully... That is the behavior I was expecting :) previous workunits with Max elapsed time should have been corrected by database change, and the exit code 239 was fixed with version 6.12 of the beta application. Thanks, -Uplinger |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
At this point, half of the new workunits have gone out, about 2,000 results left to send. They should be of 4 types. ampc, gbp, hsp90 and tk. They all number up to _0555_ from _0000_...hope that helps people wondering the sequence. the _0000000_ should be the same for all work units.
Thanks, -Uplinger |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: 
|
It's app 6.12 and the fails were with app 6.11. --//-- edit: Was reading that the next client/server software will be able to do science version distinction i.e. if original was distributed with version X all wingman would do too, even if a new app was released. This way if they'd produce a slightly different result, the validation would not fall over as has happened in past. Then also on upgrading no running dry would be needed before upgrading. Kind off how I understand the future. The first 2 resends I got were because of 'No Reply' originally sent on 22nd of July. Wingmen ran version 6.11 and in PV-state. I'm running Beta Test 6.12. 4 hours to go before we'll know, whether they will be valid or not. BETA_ BETA_ ace_ 0000000_ 0395_ 2-- - In Progress 27/07/11 14:28:43 29/07/11 04:52:43 0.00 0.0 / 0.0  |
||
|
|
coolstream
Senior Cruncher SCOTLAND Joined: Nov 8, 2005 Post Count: 475 Status: Offline Project Badges:
|
@ Sekerob, I omitted to say that I have deployed my beta net. There is now progress, I now have 16 beta up and running. They are
----------------------------------------BETA_BETA_gbp BETA_BETA_ampc BETA_BETA_hsp90 I have enough non betas in my caches to allow the net to be deployed for a further few hours. Crunching in memory of my Mum PEGGY, cousin ROPPA and Aunt AUDREY. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, I understand, but your beta-net profile *must* have at least 1 intermittent or active science selected else they'd not save. These I/A projects generate those messages you saw.
--//-- |
||
|
|
HutchNYC
Advanced Cruncher United States Joined: Nov 27, 2005 Post Count: 97 Status: Offline Project Badges:
|
I have also observed what hera and sek reported.
----------------------------------------Just for clarification for the tech's: In the boinc manager advanced screen->under the tasks tab->the column labeled "Progress" which shows the percentage complete of the WU, will sometimes change from whatever % complete to -100% (negative 100%) and then progress forward again from the last point a few seconds later. I'm guessing that it is simply doing a re-calc of the progress when the screen updates and then fills in the new value on the next screen refresh. Not a big deal...the WU's progress along fine, but I can see how that progress indication could cause some alarm. //edit//: spelling ---------------------------------------- [Edit 1 times, last edit by HutchNYC at Jul 27, 2011 5:26:43 PM] |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
Some of my ampc's have completed with no problems other that those already reported here. Am getting tk's now so it must be nearing the end.
----------------------------------------  |
||
|
|
|