| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: New DSFL Beta |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 38
|
|
| Author |
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
You opened my eyes: Only invalids decrease the daily maximum quota. Better? No, all kinds of errors except validation-errors giving "Invalids" affects the quota. This also includes all abortion of work, even if it's server-aborted due to broken wu's, will decrease the quota. But, since the quota is doubled again for each "success"-report, the quota very quickly is back to 80 per core again...  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
An invalid result is still a result AFAICT... 1:1 taken off the 80, initial maximum for a steady device. In fact those with non-valid outcome (invalid/error) speed up the deprecation of the eighty, by that famous percentage. A low cached device will not be able to destroy 80 tasks per core in a day... which is why these messages start appearing such as ''reached quota of 30".
Anyway, the last word will never be spoken on this, the ''Invalid'' being the only that go against reliability, risking to remain in that ''repair job'' class. Does not effect beta participation **, how else to find out if a device fails a test :D --//-- ** Well maybe if you fail 80 Beta tests, but try getting those on 1 device, let alone 1 core ;>) |
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 200 Status: Offline Project Badges: 
|
Hello JSYKES,
----------------------------------------Uplinger has said that Beta DSFL work units created to test targets will be shorter than normal. Ignore the time estimates. They seldom have much meaning for Beta units. Lawrence Agreed, I'd seen that, but as type 19 Beta WU's have been running out over several hours, this differential was not anticipated - I was thinking back to the previous episode when the PC dispersing the WU's had an incorrect setting that caused all the WU's to be issued with inappropriate time stamps.....just asking the question on that basis....  |
||
|
|
widdershins
Veteran Cruncher Scotland Joined: Apr 30, 2007 Post Count: 674 Status: Offline Project Badges: 
|
It'd be nice if new betas could be posted in the beta announcement section for those of us who have a watch set on that section to save needing to check the forums a few times a day for info about new tests. widdershins ,  With so small beta sets, when you receive the forum watch email all beta WUs will have already been distributed for hours.  True, but: a) It's good to keep the routine so it doesn't get overlooked and b) If people get the e-mail they'll know to check their machines to see if they picked any up. Some people have machines which crunch away unattended for days at a time so may not notice their arrival. Getting an e-mail notice allows them to check and then prioritise the Beta units for quick returns by suspending other WU's and also check out how the Betas are performing whilst running. Which leads to better feedback for the test. |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
Received a DSFL BETA task about an hour ago, and when it started it immediately errored as have several wingmen.
----------------------------------------Project Name: Beta Test Created: 09/11/2011 15:58:40 Name: BETA_BETADSFL_00000040_0000000_0005 Minimum Quorum: 2 Replication: 2 Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 5-- - In Progress 9/11/11 17:17:10 9/13/11 07:41:10 0.00 0.0 / 0.0 BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 4-- 619 Error 9/11/11 17:14:58 9/11/11 17:16:30 0.00 0.0 / 0.0 BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 3-- 619 Error 9/11/11 17:13:04 9/11/11 17:14:26 0.00 0.0 / 0.0 BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 2-- 619 Error 9/11/11 16:00:54 9/11/11 17:12:29 0.00 0.0 / 0.0 BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 1-- 619 Error 9/11/11 15:59:12 9/11/11 16:00:26 0.00 0.0 / 0.0 BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 0-- - In Progress 9/11/11 15:59:08 9/13/11 06:23:08 0.00 0.0 / 0.0 Here is a sample Result Log (all have the same error): Result Name: BETA_ BETADSFL_ 00000040_ 0000000_ 0005_ 2-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [13:11:30] Number of tasks = 16 [13:11:30] Starting job 0,CPU time is 0.000000. Unable to open PDBQT File. [13:11:30] ZINC00117225.pdbqt size = 24 6 ./3P01.pdbqt size = 0 0 Unable to update graphics data. Application exited with RC = 0xb 13:11:31 (4221): called boinc_finish </stderr_txt> ]]> [Edit 1 times, last edit by BobCat13 at Sep 11, 2011 5:21:35 PM] |
||
|
|
Brown Pelican
Cruncher Joined: Sep 9, 2010 Post Count: 8 Status: Offline |
Mon 10 Oct 2011 22:16:49 BST World Community Grid Output file BETA_BETADSFLnew_00000015_0000000_0004_6_0 for task BETA_BETADSFLnew_00000015_0000000_0004_6 absent
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Mon 10 Oct 2011 22:16:49 BST World Community Grid Output file BETA_BETADSFLnew_00000015_0000000_0004_6_0 for task BETA_BETADSFLnew_00000015_0000000_0004_6 absent This thread is for an OLD beta test. Please leave your message at https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,31854 instead, thanks. |
||
|
|
Somervillejudson@netscape.net
Veteran Cruncher USA Joined: May 16, 2008 Post Count: 1065 Status: Offline Project Badges: 
|
Received 14 all DSFLnew errored all the others 11 pending validation with runs around 1.72-2.01 hours!
|
||
|
|
|