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: 0 hours of CPU time and vaild task |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 3
|
Author |
|
katoda
Senior Cruncher Poland Joined: Apr 28, 2007 Post Count: 170 Status: Offline Project Badges: |
I saw this very first time:
----------------------------------------Result name: E207887_ 515_ C.27.C23H15NS2Si.01541660.1.set1d06_ 0-- Status: Valid Sent time: 12-05-28 15:47:17 Return time: 12-06-05 18:40:49 CPU time (hours): 0.00 Claimed/granted BOINC credit: 0.0 / 40.9 And here is the result log: Result Name: E207887_ 515_ C.27.C23H15NS2Si.01541660.1.set1d06_ 0-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. INFO: No state to restore. Start from the beginning. INFO: No state to restore. Start from the beginning. 09:16:08 (6044): Can't set up shared mem: -1. Will run in standalone mode. INFO: No state to restore. Start from the beginning. [09:21:19] Number of jobs = 16 [09:21:19] Starting job 0,CPU time has been restored to 0.000000. [09:23:56] Finished Job #0 [09:23:56] Starting job 1,CPU time has been restored to 131.524443. [09:32:00] Finished Job #1 [09:32:00] Starting job 2,CPU time has been restored to 595.939420. Application exited with RC = 0xc000013a [11:46:01] Finished Job #2 [11:46:01] Starting job 3,CPU time has been restored to 7206.185393. [11:46:01] Skipping Job #3 [11:46:01] Starting job 4,CPU time has been restored to 7206.185393. [11:46:01] Skipping Job #4 [11:46:01] Starting job 5,CPU time has been restored to 7206.185393. [11:46:01] Skipping Job #5 [11:46:01] Starting job 6,CPU time has been restored to 7206.185393. [11:46:01] Skipping Job #6 [11:46:01] Starting job 7,CPU time has been restored to 7206.185393. [11:46:02] Skipping Job #7 [11:46:02] Starting job 8,CPU time has been restored to 7206.185393. [11:46:02] Skipping Job #8 [11:46:02] Starting job 9,CPU time has been restored to 7206.185393. [11:46:02] Skipping Job #9 [11:46:02] Starting job 10,CPU time has been restored to 7206.185393. [11:46:03] Skipping Job #10 [11:46:03] Starting job 11,CPU time has been restored to 7206.185393. [11:46:03] Skipping Job #11 [11:46:03] Starting job 12,CPU time has been restored to 7206.185393. [11:46:03] Skipping Job #12 [11:46:03] Starting job 13,CPU time has been restored to 7206.185393. [11:46:03] Skipping Job #13 [11:46:03] Starting job 14,CPU time has been restored to 7206.185393. [11:46:04] Skipping Job #14 [11:46:04] Starting job 15,CPU time has been restored to 7206.185393. [11:46:04] Skipping Job #15 11:46:07 (6044): called boinc_finish [17:53:18] Number of jobs = 16 17:53:23 (5336): called boinc_finish </stderr_txt> ]]> Looks like something went wrong, but what and why? |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Lucky you, but occasionally a host forgets to pack the runtime in the result, where the above log does show 7206 seconds at the 3rd step when it decided to go fast track home [minimum is step 3 to be useful]. Time not claimed cant be given, but credit can be, though don't ask me howits done, if there is no wingman.
BTW, there are even some hosts that never send the run times, so the techs had to implement some rules to compensate these in the credit system. --//-- |
||
|
katoda
Senior Cruncher Poland Joined: Apr 28, 2007 Post Count: 170 Status: Offline Project Badges: |
Thanks for the explanation!
---------------------------------------- |
||
|
|