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: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1506 times and has 2 replies Next Thread
marvey11
Advanced Cruncher
Germany
Joined: Apr 2, 2011
Post Count: 89
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
RC 0x100

Hey there,

usually CEP2 work units run the full 12 hours on my not-too-fast computer. So I was rather surprised when I found one today that had completed in under 9 hours. A closer look at the log, however, revealed that the work unit did not complete what I would call normally. The relevant lines from the log are these:

[14:28:05] Starting job 12,CPU time has been restored to 18833.809036.
[14:28:05] Starting new Job
[14:28:05] Qink name = fldman
[14:28:12] Qink name = gesman
[14:28:14] Qink name = scfman
Application exited with RC = 0x100
[18:14:43] Finished Job #12
[18:14:43] Starting job 13,CPU time has been restored to 31577.925493.
[18:14:43] Skipping Job #13
[18:14:43] Starting job 14,CPU time has been restored to 31577.925493.
[18:14:43] Skipping Job #14
[18:14:43] Starting job 15,CPU time has been restored to 31577.925493.
[18:14:43] Skipping Job #15
18:14:51 (6399): called boinc_finish


So what, exactly, does RC 0x100 stand for? Can't be too serious, though, since the result is now stated as "Pending Validation" instead of "Error".

Other information that might be interesting: I'm running Linux; I'm running only WCG and no other BOINC projects so there's no project switching involved; computation hasn't been suspended due to any reasons, either (in fact, the machine runs at 100%, unconditionally)

I found one other thread where this ominous RC 0x100 is mentioned. In that case however, there actually seems to have been an error (and an error message).

Thanks in advance for (hopefully) shedding light on this since I'm a little puzzled wink
Marv
----------------------------------------

[Jun 4, 2011 5:42:01 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: RC 0x100

Hi Marv,

You just found 1 thread only ;? There are more though: http://www.worldcommunitygrid.org/forums/wcg/...=0&sort=1&rows=20

You may ignore the RC x xxx Result Log entries. The program determined there was an out of bound or some other condition that made it to decide to rush to the end. In 99.99% of these cases the task turns valid, often the wingman having the identical ending.

You may check on the Result sStatus page by selecting the WU name to open the quorum detail, then select the link in the status column of the wingman.

--//--
[Jun 4, 2011 5:52:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
marvey11
Advanced Cruncher
Germany
Joined: Apr 2, 2011
Post Count: 89
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: RC 0x100

Hi SekeRob!

You just found 1 thread only ;? There are more though: http://www.worldcommunitygrid.org/forums/wcg/...=0&sort=1&rows=20

Ah, well... I know about that list of threads. My OP should rather read: "I found only one thread where there's some kind of explanation...". Sorry for that!
You may ignore the RC x xxx Result Log entries. The program determined there was an out of bound or some other condition that made it to decide to rush to the end. In 99.99% of these cases the task turns valid, often the wingman having the identical ending.

I somehow thought that this can be ignored since the result is PV and not an Error... might have been interesting to know, though.
You may check on the Result Status page by selecting the WU name to open the quorum detail, then select the link in the status column of the wingman.

Have to wait for that until my wingman has finished crunching as well.

EDIT: You were right, of course. The same thing happened in the wingman's results. So I just assume that the 0x100 in some way means that the application decided it was not worth going on with the computation...

Thanks again,
Marv
----------------------------------------

----------------------------------------
[Edit 1 times, last edit by marvey11 at Jun 10, 2011 9:32:16 PM]
[Jun 4, 2011 6:33:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread