What enhancement are you proposing?
It appears HFM does not count WU failures from core b4 when the core
reports BAD_WORK_UNIT.
A clip from the log:
[18:33:51] GUI Server started
[18:33:51] Completed 0 out of 499375 steps (0%)
[18:33:51] WARNING: Caught signal SIGILL(4) on PID 3580
[18:33:51] WARNING: Unexpected exit from science code
[18:33:51] Saving result file logfile_09.txt
[18:33:51] Saving result file checkpt
[18:33:51] Saving result file log.txt
[18:33:51] Saving result file protomol.conf
[18:33:51] Saving result file ww.150.pos
[18:33:51] Saving result file ww.150.vel
[18:33:51] Saving result file ww.dcd
[18:33:51] Folding@home Core Shutdown: BAD_WORK_UNIT
[18:33:54] CoreStatus = 72 (114)
[18:33:54] Sending work to server
[18:33:54] Project: 10014 (Run 4419, Clone 0, Gen 2)
[18:33:54] - Read packet limit of 540015616... Set to 524286976.
[18:33:54] + Attempting to send results [April 15 18:33:54 UTC]
[18:33:54] - Reading file work/wuresults_09.dat from core
[18:33:54] (Read 51150 bytes from disk)
[18:33:54] Connecting to http://129.74.85.15:8080/
[18:34:04] Posted data.
[18:34:04] Initial: 0000; - Uploaded at ~5 kB/s
[18:34:04] - Averaged speed for that direction ~7 kB/s
[18:34:04] + Results successfully sent
[18:34:04] Thank you for your contribution to Folding@Home.
It does count EARLY_UNIT_END failures.
What is the expected output for the proposed enhancement?
count both E_U_E and B_W_U as failures.
What version of the product are you using?
4.11-161
Original issue reported on code.google.com by cprichar...@gmail.com on 15 Apr 2010 at 7:16
Original issue reported on code.google.com by
cprichar...@gmail.com
on 15 Apr 2010 at 7:16