| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Clean Energy Project - Phase 2 Beta Feb 24, 2016 [ Issues Thread ] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 114
|
|
| Author |
|
|
ThreadRipper
Veteran Cruncher Sweden Joined: Apr 26, 2007 Post Count: 1320 Status: Offline Project Badges: 
|
I got this Beta WU on a Win7 PC and it ran under 2 hours (finishing only job 0) and it was marked "Invalid":
----------------------------------------BETA_E236296_943_S.326.C37H33N9O1.YRSKSLDBSYGFMH-UHFFFAOYSA-N.17_s1_14 This seems as an oddity since I usually do not have invalid results.  Join The International Team: https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=CK9RP1BKX1 AMD TR2990WX @ PBO, 64GB Quad 3200MHz 14-17-17-17-1T, RX6900XT @ Stock AMD 3800X @ PBO AMD 2700X @ 4GHz |
||
|
|
widdershins
Veteran Cruncher Scotland Joined: Apr 30, 2007 Post Count: 674 Status: Offline Project Badges: 
|
I had a unit BETA_ E236294_ 988_ S.316.C31H24N4O6S1Si1.AOSWRWZVLXDPAN-UHFFFAOYSA-N.2_ s1_ 14_ 2-- which it appears was progressing but ran out of time.
The message was <snip> [16:50:04] Qink name = gesman [16:50:07] Qink name = scfman [17:17:29] Qink name = anlman [17:17:29] Qink name = drvman [17:22:29] Qink name = optman [17:22:30] Qink name = fldman [17:22:30] Qink name = gesman [17:22:34] Qink name = scfman [17:49:18] Qink name = anlman [17:49:18] Qink name = drvman Killing job because cpu time limit has been exceeded. 0.000000||64800.870000||0.000000 [17:51:38] Finished Job #0 17:51:40 (7343): called boinc_finish With this job the wingmen also failed to complete, but on the other few betas I've had that errored the wingmen were successful. The machine is usually 100% reliable in crunching WU's. |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
I had a unit BETA_ E236294_ 988_ S.316.C31H24N4O6S1Si1.AOSWRWZVLXDPAN-UHFFFAOYSA-N.2_ s1_ 14_ 2-- which it appears was progressing but ran out of time. The message was <snip> [16:50:04] Qink name = gesman [16:50:07] Qink name = scfman [17:17:29] Qink name = anlman [17:17:29] Qink name = drvman [17:22:29] Qink name = optman [17:22:30] Qink name = fldman [17:22:30] Qink name = gesman [17:22:34] Qink name = scfman [17:49:18] Qink name = anlman [17:49:18] Qink name = drvman Killing job because cpu time limit has been exceeded. 0.000000||64800.870000||0.000000 [17:51:38] Finished Job #0 17:51:40 (7343): called boinc_finish With this job the wingmen also failed to complete, but on the other few betas I've had that errored the wingmen were successful. The machine is usually 100% reliable in crunching WU's. The result you posted is an error task. Some tasks that end up being labeled as errors should really be listed as invalid. Here is an explanation from Uplinger. The work unit you have in question going from PV to error is because the Nuclear energy returned is outside of the accepted threshold given to us by the researchers. The other question is, should this be considered invalid instead. Probably, I can take a look into that. Thanks, -Uplinger The task being outside of parameters is not listed in the results log so to the eye it looks good.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
----------------------------------------  [Edit 1 times, last edit by nanoprobe at Mar 3, 2016 9:04:37 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
bump
CEP Beta issues are being posted to the New Project Beta thread. |
||
|
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 815 Status: Offline Project Badges:
|
Not sure if this has been posted yet but one of my CEP BETAs needed to be sent to 4 ppl (not an issue) resulting 2 valids (9.8 hours, 14.9 hours) and 2 errors (18 hours each)
----------------------------------------BETA_E236297_763_S.322.C40H29N3O4.OCJSFTLPEFYKOF-UHFFFAOYSA-N.1_s1_14 (Screenshot link) Edit: Why it resulted in invalids for 2 ppl after running 18 hours and resulted in valids for 2 other ppl is confusing me.  [Edit 1 times, last edit by Seoulpowergrid at Mar 8, 2016 2:12:29 AM] |
||
|
|
KWSN-A Shrubbery
Senior Cruncher Joined: Jan 8, 2006 Post Count: 476 Status: Offline Project Badges:
|
Because even after 18 hours those computers did not do enough processing to validate the first job. Some tasks are monsters and only the fastest computers will get far enough.
---------------------------------------- |
||
|
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 815 Status: Offline Project Badges:
|
Because even after 18 hours those computers did not do enough processing to validate the first job. Some tasks are monsters and only the fastest computers will get far enough. Clicking on the "result log" it is showing it never finished the first task for both wingman machines that it failed on. I was getting confused as I thought it ran on my fastest machine, but in reality it ran on a much slower machine.Ah ha~ Now it makes sense. Thanks for the info. |
||
|
|
numbacruncher
Cruncher Joined: Oct 5, 2007 Post Count: 3 Status: Offline Project Badges: 
|
BETA_E236294_419_S.316.C36H24N4O2S2.RPPZYYJTQWJOKQ-UHFFFAOYSA-N.14_s1_14
This WU runs in an endless loop and is repeating and repeating again. "07.03.2016 21:52:52 | World Community Grid | Task BETA_E236294_419_S.316.C36H24N4O2S2.RPPZYYJTQWJOKQ-UHFFFAOYSA-N.14_s1_14_2 exited with zero status but no 'finished' file" |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Your 'exit zero status' hints and a system overload. Rules of thumb for CEP2 [and the Beta's of course]:
1) Start with running only 1 to confirm system is up to it. 2) Ensure LAIM (Leave Application in Memory, when suspended) is on, else the task unloads and goes back to zero, or last checkpoint each time it is interrupted. 3) Start with CEP2 computing only when user is *not* active. This work is heavy, the disk part of the model can exceed 2GB, loads of disk I/O. 4) When user is in-active, give maximum amount of memory/RAM... the more allowed for BOINC, the less disk I/O occurs [theory]. 5) Make sure the Virtual Memory / Swap file use allowance is big enough. Set auto-expansion in your system with a minimum size, to avoid fragmentation. Probably not all, but these are items I can think of at this time. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Because even after 18 hours those computers did not do enough processing to validate the first job. Some tasks are monsters and only the fastest computers will get far enough. I have one that suffered this fate and was marked as an error too. BETA_ E236297_ 886_ S.326.C38H33N5O2Si1.ABVUNPPUYRFYMH-UHFFFAOYSA-N.16_ s1_ 14_ 1-- Surely there must be a better way than to just throw 18 hours of work at a time away and give the client no credit? Can't we let the client run until it finishes the first job? |
||
|
|
|