Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 532 times and has 1 reply Next Thread
Thyme Lawn
Cruncher
Joined: Dec 9, 2008
Post Count: 46
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Exit with RC=0xc000013a and low reported CPU time

WU 887376973

E216969_492_I.47.C34F6H15N5O2.00025081.2.set1d06_3-- 	640 	Valid 	24/11/13 14:52:37 	25/11/13 14:58:50 	12.00 	269.7 / 114.5
E216969_492_I.47.C34F6H15N5O2.00025081.2.set1d06_2-- 640 Valid 24/11/13 14:28:26 25/11/13 04:46:41 12.00 238.3 / 141.0
E216969_492_I.47.C34F6H15N5O2.00025081.2.set1d06_1-- - No Reply 14/11/13 14:19:40 24/11/13 14:19:40 0.00 0.0 / 0.0
E216969_492_I.47.C34F6H15N5O2.00025081.2.set1d06_0-- 640 Valid 14/11/13 14:00:59 25/11/13 06:44:44 0.56 10.1 / 32.5

Result ids are:

_0 - 1684343923
_2 - 1704790415
_3 - 1704846106

The _2 and _3 tasks reached the CPU time limit in phase 12 and their credit claims were dragged down by _0's low claim.

The _0 task exited with RC = 0xc000013a (application terminated as a result of a CTRL+C) in phase 2 with reported CPU time of 0.56 hours and a claimed credit 10.1. The stderr_txt output indicates there were 8 attempts to run phase 2, with the time stamps suggesting that it would have taken longer than the computer is switched on for. The wall time for the 8th attempt to run phase 2 (the one generating the exit condition) was 9:48:08 and the restored CPU time on skipping phases 3 to 15 was 20257.229053 seconds (5.63 hours, 5.07 hours greater than the reported CPU time).

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[10:35:45] Number of jobs = 16
[10:35:45] Starting job 0,CPU time has been restored to 0.000000.
[10:53:29] Finished Job #0
[10:53:29] Starting job 1,CPU time has been restored to 526.596976.
[11:41:56] Finished Job #1
[11:41:56] Starting job 2,CPU time has been restored to 2013.489307.
[16:09:41] Number of jobs = 16
[16:09:41] Starting job 2,CPU time has been restored to 2013.489307.
[08:38:33] Number of jobs = 16
[08:38:33] Starting job 2,CPU time has been restored to 2013.489307.
[17:57:18] Number of jobs = 16
[17:57:18] Starting job 2,CPU time has been restored to 2013.489307.
[08:47:32] Number of jobs = 16
[08:47:32] Starting job 2,CPU time has been restored to 2013.489307.
[08:43:03] Number of jobs = 16
[08:43:03] Starting job 2,CPU time has been restored to 2013.489307.
[08:44:14] Number of jobs = 16
[08:44:14] Starting job 2,CPU time has been restored to 2013.489307.
[08:24:48] Number of jobs = 16
[08:24:48] Starting job 2,CPU time has been restored to 2013.489307.
Application exited with RC = 0xc000013a
[18:12:56] Finished Job #2
[18:12:56] Starting job 3,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #3
[18:12:56] Starting job 4,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #4
[18:12:56] Starting job 5,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #5
[18:12:56] Starting job 6,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #6
[18:12:56] Starting job 7,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #7
[18:12:56] Starting job 8,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #8
[18:12:56] Starting job 9,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #9
[18:12:56] Starting job 10,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #10
[18:12:56] Starting job 11,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #11
[18:12:56] Starting job 12,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #12
[18:12:56] Starting job 13,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #13
[18:12:56] Starting job 14,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #14
[18:12:56] Starting job 15,CPU time has been restored to 20257.229053.
[18:12:56] Skipping Job #15
18:13:01 (2712): called boinc_finish
[08:43:52] Number of jobs = 16
08:43:59 (1108): called boinc_finish

</stderr_txt>
]]>

----------------------------------------
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer
[Nov 26, 2013 11:55:27 AM]   Link   Report threatening or abusive post: please login first  Go to top 
armstrdj
Former World Community Grid Tech
Joined: Oct 21, 2004
Post Count: 695
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Exit with RC=0xc000013a and low reported CPU time

CEP2 is a unique project in that it returns success if part of the workunit does not complete properly. Most of the time this is expected to match across multiple copies but this is not always the case. For this example the CPU time for job 2 was not counted since it failed. We will look into a better way to handle this.

Thanks,
armstrdj
[Dec 4, 2013 9:31:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread