| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: FightAIDS@Home Beta Test Feb 13, 2013 (Issues Thread) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 90
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This is interesting. I apparently processed these WU's for a number of real time hours and used zero cpu time. I have another with the boinc client showing 7+ hours elapsed at 0% completion. Update: that WU just reported completed with 7.7 hrs RT and also 0 cpu time. Quite frankly I am at a loss but here are the environments:
----------------------------------------Phenom II x4 3.0, 4GB, Fedora-18-x86_64, client 7.0.29 running as a service (systemctl) Athlon64 x2 2.2, 2GB, Fedora-18-x86_64, Client 7.0.29 running as a service. BETA_ faah38222_ ZINC09219383_ xPR_ wC6_ 11_ 1ref9_ 00_ 1-- starbase2.comma nd Pending Validation 2/13/13 20:59:27 2/14/13 01:45:06 0.00 / 4.72 44.9 / 0.0 BETA_ faah38222_ ZINC14140957_ xPR_ wC6_ 11_ 1ref9_ 01_ 2-- starbase2.comma nd Valid 2/13/13 20:56:49 2/14/13 03:20:26 0.00 / 6.12 58.3 / 58.3 BETA_ faah38222_ ZINC06600483_ xPR_ wC6_ 11_ 1ref9_ 01_ 1-- starbase2.comma nd Pending Validation 2/13/13 20:54:44 2/14/13 01:33:53 0.00 / 4.35 41.4 / 0.0 BETA_ faah38221_ ZINC14368363_ xPR_ wC6_ 11_ 1ref9_ 01_ 2-- starbase2.comma nd Pending Validation 2/13/13 19:53:16 2/14/13 03:25:06 0.00 / 6.20 59.0 / 0.0 BETA_ faah38221_ ZINC09986295_ xPR_ wC6_ 11_ 1ref9_ 04_ 0-- starbase1.comma nd Valid 2/13/13 19:33:27 2/14/13 04:08:25 0.00 / 7.18 47.2 / 57.6 Edit, Update 2: The last WU completed normally on my 32 bit laptop... BETA_ faah38222_ ZINC09378128_ xPR_ wC6_ 11_ 1ref9_ 03_ 0-- starbase3.comma nd Pending Validation 2/13/13 21:00:22 2/14/13 13:46:48 13.37 / 15.63 93.9 / 0.0 Environment: Centrino 1.6, 1.5GB, Fedora-17 i386 client 7.0.29 running as a service. Does this mean I get zero time for the x64 6 WU's work? [Edit 1 times, last edit by Former Member at Feb 14, 2013 4:42:37 PM] |
||
|
|
themoonscrescent
Veteran Cruncher UK Joined: Jul 1, 2006 Post Count: 1320 Status: Offline Project Badges: 
|
I've had 3 (1 on each of my I7's), error out straight away, no time wasted, almost all the others that are currently crunching and seem to be okay.
----------------------------------------  |
||
|
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
Spread across 7? systems with more specs than anyone cares about all of mine have either completed successfully or will shortly. Validation appears to be proceeding normally. I think you nailed this one.
---------------------------------------- Distributed computing volunteer since September 27, 2000 |
||
|
|
ca05065
Senior Cruncher Joined: Dec 4, 2007 Post Count: 325 Status: Offline Project Badges: 
|
Two of my BETA work units restarted correctly after overnight shutdown
BETA_ faah38222_ ZINC14900848_ xPR_ wC6_ 11_ 1ref9_ 03_ 0-- colina-PC Pending Validation 2/13/13 21:08:58 2/14/13 08:06:09 3.94 / 3.96 120.7 / 0.0 BETA_ faah38222_ ZINC17964115_ xPR_ wC6_ 11_ 1ref9_ 01_ 0-- colina-PC Pending Validation 2/13/13 21:08:58 2/14/13 07:55:43 3.75 / 3.77 114.8 / 0.0 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hmm mine is at 66% after 2 hours and 42 minutes of CPU time so it should end pretty faster than normal FAAH units. Usually they take between 5-7 hours in my PC(AMD Athlon II X2 445 3.51 GHZ) Whatever you see, the WU numbers indicate we're running a set out of experiment 41 that already went through production, which is an excellent test case to find if the outcome of the new app matches the outcome of the old app. Got 2 on duo, 8 on octo Win, none on Linux... it said the device was over-committed and new work would not finish in time, so no work assigned 2/13/2013 9:23:50 PM Tasks won't finish in time: BOINC runs 99.7% of the time; computation is enabled 100.0% of that ;( (4 days cache, and the lot is due in 3.8 days, and not going to abort because of ;) |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges: 
|
All went w/o problems, checked checkpoints for 2 - 3 of them, restarted correctly.
----------------------------------------Interesting insight (at least for me, I thought it is otherwise): normal GPU tasks have priority over CPU Betas. Currently status: - Win 7 64, i7-3770, 7.0.48 using app_config to crunch 12 GPU's on 3 CPU threads: 8 Valid + 5 PVal, CPU Time from 2.62 hours to 4.05 hours - Mac OS X Mountain Lion (64-bit), i5-2500S, 7.0.31: all 7 PVal, CPU Time from 3.62 hours to 7.02 hours (majority in range 3.62 - 4.24 h) So far so good (knocking on wood)   Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006  [Edit 1 times, last edit by branjo at Feb 14, 2013 9:32:34 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Got one that was server aborted, not a trace in the message logs of that [why?] except for the RtR acknowledgement [because I have this log flag on], and most persistently misleading, these SA's keep being reported on the RS pages as "Error" instead of Server Aborted.
4639 World Community Grid 2/14/2013 10:59:40 AM [sched_op] Starting scheduler request 4640 World Community Grid 2/14/2013 10:59:40 AM Sending scheduler request: To report completed tasks. 4641 World Community Grid 2/14/2013 10:59:40 AM Reporting 1 completed tasks 4642 World Community Grid 2/14/2013 10:59:40 AM Not requesting tasks: don't need 4643 World Community Grid 2/14/2013 10:59:40 AM [sched_op] CPU work request: 0.00 seconds; 0.00 devices 4644 World Community Grid 2/14/2013 10:59:44 AM Scheduler request completed 4645 World Community Grid 2/14/2013 10:59:44 AM [sched_op] Server version 701 4646 World Community Grid 2/14/2013 10:59:44 AM Project requested delay of 11 seconds 4647 World Community Grid 2/14/2013 10:59:44 AM [sched_op] handle_scheduler_reply(): got ack for task BETA_faah38222_ZINC54394603_xPR_wC6_11_1ref9_02_3 BETA_ faah38222_ ZINC54394603_ xPR_ wC6_ 11_ 1ref9_ 02_ 3-- 711 Error 2/13/13 22:08:37 2/14/13 09:59:40 0.00 122.6 / 0.0 < moi BETA_ faah38222_ ZINC54394603_ xPR_ wC6_ 11_ 1ref9_ 02_ 0-- 711 Valid 2/13/13 21:36:26 2/14/13 09:46:50 7.66 177.0 / 142.3 BETA_ faah38222_ ZINC54394603_ xPR_ wC6_ 11_ 1ref9_ 02_ 1-- 711 Valid 2/13/13 21:36:22 2/14/13 06:25:58 4.64 107.5 / 142.3 BETA_ faah38222_ ZINC54394603_ xPR_ wC6_ 11_ 1ref9_ 02_ 2-- 711 Error 2/13/13 21:36:13 2/13/13 22:08:32 0.03 1.0 / 0.0 No second of computing time and having a 122.6 "claim" [all the more proof that claims are not client issued... what's the computation behind this?] is of course another point that could use a fix [and not confuse the starting cruncher]. Still here for the long haul! |
|||
|
||||
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: 
|
Got one that was server aborted, not a trace in the message logs of that [why?] except for the RtR acknowledgement [because I have this log flag on], and most persistently misleading, these SA's keep being reported on the RS pages as "Error" instead of Server Aborted. . . No second of computing time and having a 122.6 "claim" [all the more proof that claims are not client issued... what's the computation behind this?] is of course another point that could use a fix [and not confuse the starting cruncher]. Still here for the long haul! I noticed too that there is no single line in the message log when a task is server aborted. The 'Error' on your results page is because of the incompatibility of the BOINC clients exit codes of version 6 and 7. You will have v7 running and the WCG-server code is not updated yet to interpret all v7 exit codes right. I had a server aborted task too and by chance it was on the only host where I have still BOINC 6 running. On my results page that task is "Server aborted" due to 2 wingmen ready and mine not started. BETA_ faah38222_ ZINC12553895_ xPR_ wC6_ 11_ 1ref9_ 02_ 2-- 711 Server Aborted 13/02/13 21:38:35 14/02/13 08:00:33 0.00 122.3 / 0.0 BETA_ faah38222_ ZINC12553895_ xPR_ wC6_ 11_ 1ref9_ 02_ 1-- 711 Valid 13/02/13 21:38:20 14/02/13 07:25:14 4.84 129.5 / 105.1 BETA_ faah38222_ ZINC12553895_ xPR_ wC6_ 11_ 1ref9_ 02_ 0-- 711 Valid 13/02/13 21:38:18 14/02/13 07:54:52 5.53 80.6 / 105.1 As you can see also a claim without done anything.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Still not one beta for my machine...
 Still wishing there is a facility in BOINC where WUs of a type (in this case, beta-WUs) can be 'ordered' on demand (regardless of beta enrolment or non-enrolment). Without that I get the regulars (as reflected in my project-settings webpage) and the WU-requesting machine gets flooded with those regulars, possibly crowding out the beta-WUs.; ; andzgridPost#945 ; |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3294 Status: Offline Project Badges: 
|
My WU finished at 3 hours and 55 minutes of CPU.
----------------------------------------AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
|