| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: The Clean Energy Project - Phase 2 Forum
Thread: Killing Job because CPU time has been exceeded |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Dayle Diamond
Senior Cruncher Joined: Jan 31, 2013 Post Count: 447 Status: Offline Project Badges: 
|
This one work unit has been failing over and over again on different computers. It's eating up 18 hours of CPU time each iteration. Even my 4930k wasn't fast enough for it.
Techs, can you pull it? Result Name: E235857_ 708_ S.304.C35H27N5O4.QBQMMVRBLMTAPO-UHFFFAOYSA-N.8_ s1_ 14_ 2-- <core_client_version>7.6.22</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [17:40:52] Number of jobs = 8 [17:40:52] Starting job 0,CPU time has been restored to 0.000000. Killing job because cpu time has been exceeded. Subjob start time = 0, Subjob current time = 0 [11:52:33] Finished Job #0 11:52:34 (1032): called boinc_finish </stderr_txt> ]]> |
||
|
|
noderaser
Senior Cruncher United States Joined: Jun 6, 2006 Post Count: 297 Status: Offline Project Badges: 
|
There is a maximum number of replications sent out for each subproject, after that it gets flagged as bad, so it won't be floating around out there forever.
---------------------------------------- |
||
|
|
|