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: 5
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 5314 times and has 4 replies Next Thread
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
CEP2 Result Log incomplete, Windows v 6.35

My quad currently on a testing mission running W7-64 completed a result which ran the maximum 12:00 hours per the BOINCTasks history and also per the Result Status page:

E200529_ 751_ A.26.C20H10N2S3Si.1.4.set1d06_ 0-- 635 Valid 12-11-10 20:20:25 14-11-10 00:44:16 12.00 137.5 / 179.0
E200529_ 751_ A.26.C20H10N2S3Si.1.4.set1d06_ 1-- 635 Valid 12-11-10 20:20:19 14-11-10 16:06:59 12.00 220.6 / 179.0 < Moi

Curious to know how far mine got compared to the wingman, looked in and saw the below:

My Result Log:

Result Name: E200529_ 751_ A.26.C20H10N2S3Si.1.4.set1d06_ 1--
<core_client_version>6.12.6</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[04:41:13] Number of jobs = 16
[04:41:13] Starting job 0,CPU time has been restored to 0.000000.
[04:44:46] Finished Job #0
[04:44:46] Starting job 1,CPU time has been restored to 204.782513.
[04:53:55] Finished Job #1
[04:53:55] Starting job 2,CPU time has been restored to 740.879949.
[08:16:19] Finished Job #2
[08:16:19] Starting job 3,CPU time has been restored to 12599.919968.
[08:26:55] Finished Job #3
[08:26:55] Starting job 4,CPU time has been restored to 13208.230268.
[08:34:09] Finished Job #4
[08:34:09] Starting job 5,CPU time has been restored to 13624.487736.
[08:41:40] Finished Job #5
[08:41:40] Starting job 6,CPU time has been restored to 14061.820939.
[08:48:48] Finished Job #6
[08:48:48] Starting job 7,CPU time has been restored to 14478.718012.
[08:58:56] Finished Job #7
[08:58:56] Starting job 8,CPU time has been restored to 15075.203435.
[09:06:01] Finished Job #8
[09:06:01] Starting job 9,CPU time has been restored to 15469.495963.
[09:13:26] Finished Job #9
[09:13:26] Starting job 10,CPU time has been restored to 15907.811972.
[09:29:56] Finished Job #10
[09:29:56] Starting job 11,CPU time has been restored to 16878.699796.
[09:39:35] Finished Job #11
[09:39:35] Starting job 12,CPU time has been restored to 17446.574636.
[11:09:57] Finished Job #12
[11:09:57] Starting job 13,CPU time has been restored to 22758.814289.
[13:15:47] Finished Job #13
[13:15:47] Starting job 14,CPU time has been restored to 30023.827659.
[15:19:08] Finished Job #14
[15:19:08] Starting job 15,CPU time has been restored to 37283.178193.

</stderr_txt>
]]>

Wingman Result Log:

Result Name: E200529_ 751_ A.26.C20H10N2S3Si.1.4.set1d06_ 0--
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[09:48:57] Number of jobs = 16
[09:48:57] Starting job 0,CPU time has been restored to 0.000000.
[09:52:22] Finished Job #0
[09:52:22] Starting job 1,CPU time has been restored to 199.234375.
[10:02:31] Finished Job #1
[10:02:31] Starting job 2,CPU time has been restored to 794.937500.
[14:11:51] Finished Job #2
[14:11:51] Starting job 3,CPU time has been restored to 14572.218750.
[14:23:22] Finished Job #3
[14:23:22] Starting job 4,CPU time has been restored to 15241.984375.
[14:30:41] Finished Job #4
[14:30:41] Starting job 5,CPU time has been restored to 15672.468750.
[14:38:50] Finished Job #5
[14:38:50] Starting job 6,CPU time has been restored to 16152.125000.
[14:46:25] Finished Job #6
[14:46:25] Starting job 7,CPU time has been restored to 16601.390625.
[14:56:36] Finished Job #7
[14:56:36] Starting job 8,CPU time has been restored to 17201.843750.
[15:04:14] Finished Job #8
[15:04:14] Starting job 9,CPU time has been restored to 17654.687500.
[15:13:41] Finished Job #9
[15:13:41] Starting job 10,CPU time has been restored to 18168.796875.
[15:33:08] Finished Job #10
[15:33:08] Starting job 11,CPU time has been restored to 19264.343750.
[15:43:45] Finished Job #11
[15:43:45] Starting job 12,CPU time has been restored to 19889.078125.
[17:15:15] Finished Job #12
[17:15:15] Starting job 13,CPU time has been restored to 25330.687500.
[20:01:23] Finished Job #13
[20:01:23] Starting job 14,CPU time has been restored to 34183.109375.
[22:21:08] Finished Job #14
[22:21:08] Starting job 15,CPU time has been restored to 42360.765625.
Killing job because cpu time has been exceeded. Subjob start time = -2147483648, Subjob current time = 1088728856
[22:35:35] Finished Job #15
22:35:50 (6056): called boinc_finish

</stderr_txt>
]]>


From these 2 logs it appears my quad did get further in starting job 15 (the 16th really) at 37283 seconds (10.35 hours) and the wingman at 42360 seconds (11.76 hours). That for statistics, what is odd is that the "killing job" part is missing. Nothing in the client message log indicates an event:

834 WCG 14-11-2010 17:00:44 Computation for task E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1 finished
835 WCG 14-11-2010 17:00:44 [dcf] DCF: 1.315500->1.527059, raw_ratio 1.527059, adj_ratio 1.160820
836 WCG 14-11-2010 17:00:44 Starting c4cw_target02_051019134_0
837 WCG 14-11-2010 17:00:44 [cpu_sched] Starting c4cw_target02_051019134_0 (initial)
838 WCG 14-11-2010 17:00:44 Starting task c4cw_target02_051019134_0 using c4cw version 613
839 WCG 14-11-2010 17:01:03 Started upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_0
840 WCG 14-11-2010 17:01:03 Started upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_1
841 WCG 14-11-2010 17:01:03 Started upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_2
842 WCG 14-11-2010 17:01:07 Finished upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_0
843 WCG 14-11-2010 17:01:07 Started upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_3
844 WCG 14-11-2010 17:01:10 Finished upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_2
845 WCG 14-11-2010 17:01:10 Finished upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_3
846 WCG 14-11-2010 17:01:10 Started upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_4
847 WCG 14-11-2010 17:01:12 Finished upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_1
848 WCG 14-11-2010 17:01:37 [checkpoint] result c4cw_target02_051025434_0 checkpointed
856 WCG 14-11-2010 17:06:36 [checkpoint] result E200529_783_A.26.C19H10N2OS4.185.1.set1d06_1 checkpointed
857 WCG 14-11-2010 17:06:47 Finished upload of E200529_751_A.26.C20H10N2S3Si.1.4.set1d06_1_4
858 WCG 14-11-2010 17:06:49 [sched_op] Starting scheduler request
859 WCG 14-11-2010 17:06:49 Sending scheduler request: To report completed tasks.
860 WCG 14-11-2010 17:06:49 Reporting 1 completed tasks, not requesting new tasks
861 WCG 14-11-2010 17:06:49 [sched_op] CPU work request: 0.00 seconds; 0.00 CPUs

Validated of course, is this a bug or a feature and more importantly, was the complete result zipped and transmitted?
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at Nov 14, 2010 5:02:39 PM]
[Nov 14, 2010 5:00:00 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Result Log incomplete, Windows v 6.35

Killing job because cpu time has been exceeded. Subjob start time = -2147483648, Subjob current time = 1088728856

I am not quite sure what you are saying. I have many WUs with a completion time of >16 hours. And I have not seen the Killing message you describe.
[Nov 14, 2010 7:12:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Result Log incomplete, Windows v 6.35

Strange, just sorted all CEP2 jobs on my RS pages and except for this one all with 12.00 hours (not many) have the killing line.

As for yours >16 hours, *off topic*, if not a typo, indicating a very poor efficiency >>>> See the CEP2 forum and the "To Defrag, Not to Defrag" topic in BOINC support for discussions.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Nov 14, 2010 7:26:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Result Log incomplete, Windows v 6.35

I see what you mean. I did that sort and I have only one WU with 12 hours. When I look at the results for that one, I see...

[04:34:09] Starting job 15,CPU time has been restored to 27044.832563.
Killing job because cpu time has been exceeded. Subjob start time = 1219963127, Subjob current time = 1088055605
[09:07:48] Finished Job #15
09:07:59 (5444): called boinc_finish

When I was referring to >16 hours, this was from the WCG - BOINC advanced view for the "To completion" column.
----------------------------------------
[Edit 1 times, last edit by Former Member at Nov 14, 2010 7:40:47 PM]
[Nov 14, 2010 7:37:23 PM]   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: CEP2 Result Log incomplete, Windows v 6.35

Sek,

You should have seen the text in the error log that it was ending early. Not sure why this is absent in this case. But the output zip file is required and if it had not been transmitted properly that result would have moved to an error state. Let me know if you see more of these and I will take a look.

Thanks,
armstrdj
[Nov 15, 2010 2:57:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread