| 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 starting Nov 6, 2013 v7.24 [ Issues Thread ] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 130
|
|
| Author |
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
This thread exists to discuss the new round of beta testing announced in this thread: https://secure.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=437179
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
Note: There have been comments about the large variation in runtime for the project. This is going to be a permanent of the project. The nature of this project makes it impossible to consistently size the jobs. As such expect to see a large variation in the runtime for each task.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Glad you put the finger on the sore spot, and glad you froze the DCF to 1.000000 [albeit this only working for v7 clients].
----------------------------------------Now, the hunt is on for those 7.24 to run on me W7-64 service installed client. So far, no work. edit: And the good news is, after re-selecting Beta testing for the 'service' running device  , that the first 3 of 7.24 got past the 10 second mark... 3 minutes and counting.edit2: And the funny is, the 4th received was a 7.22 repair job... it immediately started with the zero status exit cycle, whilst the 7.24 stoically continued crunching, now 8 minutes with progresses % incrementing. Send the 7.22 to it's hereafter pastures. :D [Edit 2 times, last edit by Former Member at Nov 6, 2013 3:27:04 PM] |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
Note: There have been comments about the large variation in runtime for the project. This is going to be a permanent of the project. The nature of this project makes it impossible to consistently size the jobs. As such expect to see a large variation in the runtime for each task. Thanks much for this information. My run times yesterday were all over the map and I was wondering about it. I am running 44 right now and will see what happens.   |
||
|
|
BoincST
Cruncher Joined: Feb 25, 2010 Post Count: 12 Status: Offline Project Badges:
|
Just completed two in a very short time:
----------------------------------------BETA_ BETA_ 9999979_ 0228d_ 0-- 2174649 Pending Validation 06.11.13 14:48:22 06.11.13 14:54:39 0.05 / 0.05 1.4 / 0.0 BETA_ BETA_ 9999979_ 0225d_ 1-- 2174649 Pending Validation 06.11.13 14:48:22 06.11.13 14:51:30 0.02 / 0.02 0.5 / 0.0 I got four more WU. Two are running and checkpointing (every 10 minutes) just how I like them  Another one was stuck for 10 minutes at 0,500%. Now the percentage is going up, but no checkpoint until now (15 minutes). Edit: First checkpoint after 18 minutes, second 28 minutes. The last one ist stuck for now 15 minutes at 0,500%, but checkpointed at 10:00. Edit: Second checkpoint at 26:35 and 1,414% [Edit 3 times, last edit by BoincST at Nov 6, 2013 3:32:45 PM] |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1322 Status: Offline Project Badges: 
|
Now, the hunt is on for those 7.24 to run on me W7-64 service installed client. So far, no work. No hunting, just luck:After having looking 2 hours to a black screen with CHKDSK info and following reboot, the first thing I saw was arriving 3 7.24 tasks on my Windows Vista64 quad without service install for BOINC. 4th core outside of BOINC very busy with an RNA World VM. The 0.5% init phase is also very different in time of those three tasks. Edit: Forgot to mention: 2 of the 3 tasks are 32bit versions. Edit again: Mind I saw a ghost with this task on Server 2008 service install: BETA_BETA_9999981_0552d_1 using beta17 version 724 in slot 41 At 14 seconds runtime it showed 100% done and disappered, what wasn't true, because it jumped down the queue sorted on progress to 0.5%. [Edit 3 times, last edit by Crystal Pellet at Nov 6, 2013 3:38:27 PM] |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
Got just 1 of these v7.24 WUs, and it's on my Q9650, Win 7-x64, BOINC 7.0.64, service install.
It's purring along quite happily, 31% complete after 34 min, last checkpoint at 26 min. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
All 8 cores of the W7-64 humming along with one stuck to 0.500% after half an hour and no checkpoint. For the nervous types, if you navigate to the appropriate job slot, seen in job properties of the BM, [structure could be hidden requiring the path to be typed as sub from where the data_dir is as printed in event log at top], then open up the stderr.txt file in notepad or other ASCII text editor/viewer. Then you get the view something like this, which shows that actually the first computing pass (0) was scaled, indicating that all is fine, up to that point:
----------------------------------------Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.24_windows_x86_64 -SettingsFile BETA_9999982_0400d.txt -DatabaseFile dataset-GDS2771-v1.txt Initializing wcg_learn_limit = 250000 Running INFO: WcgLearnLimit(250000) reached. 0.9184007985596736 0.0622189357504794 INFO: WcgLearnLimit(250000) reached. 1.7245591172529657 0.0036618170975089 INFO: WcgLearnLimit(250000) reached. 1.4943797402393102 0.2484098818163147 INFO: WcgLearnLimit(250000) reached. 1.1770141398737906 0.0271241741984340 INFO: WcgLearnLimit(250000) reached. 1.0493408828623387 0.4672734253881572 INFO: WcgLearnLimit(250000) reached. 1.8702338274791259 0.2873483948776539 INFO: WcgLearnLimit(250000) reached. 0.0575631726082975 0.0326153084776024 INFO: WcgLearnLimit(250000) reached. 0.1696588414824873 0.0242827797963230 INFO: WcgLearnLimit(250000) reached. 0.2321585081598414 0.0015365133441350 INFO: WcgLearnLimit(250000) reached. 0.1617702345736234 0.0528432482007020 INFO: WcgLearnLimit(250000) reached. 0.1395274012199934 0.0267079080608426 INFO: WcgLearnLimit(250000) reached. 0.2623190578883623 0.0046133714504322 INFO: WcgLearnLimit(250000) reached. 0.1370839717147874 0.0295953898428252 INFO: WcgLearnLimit(250000) reached. 0.2684822125722803 0.0172978689687397 INFO: WcgLearnLimit(250000) reached. 1.0544909225500305 0.0088792981532038 INFO: WcgLearnLimit(250000) reached. 0.4664028476445310 0.0025447455122958 INFO: WcgLearnLimit(250000) reached. 0.1696830913153917 0.0019285440335466 [16:41:11]: Computing pass 0 INFO: WcgLearnLimit(250000) reached. 1.5686208681947846 1.2800151977205587 INFO: WcgLearnLimit(250000) reached. 1.4702578928421417 1.2410766244212255 edit: Make sure to exit the txt viewer after you're done, without saving of course. If you don't it could lead to the file having remained locked and the task not able to write new data.... carash :O [Edit 1 times, last edit by Former Member at Nov 6, 2013 4:10:00 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have 4 running sweetly on this service-install Win7-64. Well done with the fix!
However, like BoincST, I received one that completed very quickly. Maybe normal, maybe not. BETA_ BETA_ 9999980_ 0224d_ 1-- Pending Validation 06/11/13 15:08:41 06/11/13 15:11:51 0.02 / 0.02 0.5 / 0.0 Just this in the Event Log: 06/11/2013 15:08:45 | World Community Grid | Starting task BETA_BETA_9999980_0224d_1 using beta17 version 724 in slot 7 06/11/2013 15:10:11 | World Community Grid | Computation for task BETA_BETA_9999980_0224d_1 finished and Result Log: Result Name: BETA_ BETA_ 9999980_ 0224d_ 1-- <core_client_version>7.0.64</core_client_version> <
|
. . . At 14 seconds runtime it showed 100% done and disappered, what wasn't true, because it jumped down the queue sorted on progress to 0.5%. I saw this also on one of my Win32 machines. In my case it ran up to 100% immediately upon starting, then settled down to 0.5% and is running normally.  |
||
|
|
|