BETA_ BETA_ 9999984_ 0421_ 0-- completed without apparent error but never checkpointed :
Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.19_windows_x86_64 -SettingsFile BETA_9999984_0421.txt -DatabaseFile dataset-GDS2771-v1.txt
Initializing
wcg_learn_limit = 1000000
Running
Run complete, CPU time: 11220.340725
10:38:18 (21056): called boinc_finish

BETA_ BETA_ 9999984_ 0503_ 0-- completed without error, but checkpointed erratically , at intervals of either 10 mins or 21 to 26 mins:
[11:03:29]: Computing pass 13
Run complete, CPU time: 14104.393612
11:21:26 (2032): called boinc_finish

BETA_ BETA_ 9999984_ 0189_ 0-- completed with Error -131 (but checkpointed ok every 10 minutes):
[10:53:52]: Computing pass 6080
Run complete, CPU time: 12356.308807
10:54:10 (12028): called boinc_finish
</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>BETA_BETA_9999984_0189_0_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>
Event Log: 31/10/2013 10:54:12 | World Community Grid | File size: 104371693.000000 bytes. Limit: 10485760.000000 bytes

BETA_ BETA_ 9999984_ 0427_ 0-- completed with Error -131 (but checkpointed ok every 10 minutes):
[10:28:45]: Computing pass 615
Run complete, CPU time: 11062.561313
10:29:05 (23448): called boinc_finish
</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>BETA_BETA_9999984_0427_0_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>
Event Log: 31/10/2013 10:29:08 | World Community Grid | File size: 11637934.000000 bytes. Limit: 10485760.000000 bytes

All the above on an i5-750, Windows7-64, BOINC 7.0.64.

As you know Rob I have given up discussing WCG's crediting years ago, particularly for historical applications like faah-autodock, and obviously I don't care about it for 2 beta WUs.

But since WCG is looking for ways to attract crunchers from other sites my edit about pph was meant to remind the staff that they should make sure not to choose a repulsive pph for this new application.

Received 2 resends.
First one errored out:
</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>BETA_BETA_9999984_0187_2_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>

Second in progress but it's already errored out twice so not expecting anything different.

These units should be killed asap, so they don't circulate and waste resources because of the output file errors.

@ Mumak,

Not really... the objective [one of them] is to determine the statistical spread and significance. Same as what we see on CEP2, a 2nd or 3rd wingman could actually complete the task without exceeding the bounds, which might point to yet other problems. The techs want know until we do repetitive attempts at those [some 5, some 7, some even 10], on different devices, different CPU's [which, yes, is my base argument to get the OS printed in the logs for the DIY diagnotiseurs, even the CPU specs].

----

Meanwhile, the only one that refuses to pass the 0.500%, no matter what I do is on a W7-32 dual core system [that's 1 out of 16 now]. The other sciences [CEP2 and FAHV] seem not to care about the 'stuck' side task. 2:10.42 hours, no checkpoint. The wingman has not reported yet either, so no secondary indication where this is going:

BETA_ BETA_ 9999986_ 0370_ 1-- - In Progress 10/31/13 06:52:27 11/10/13 06:52:27 0.00 0.0 / 0.0
BETA_ BETA_ 9999986_ 0370_ 0-- - In Progress 10/31/13 06:52:23 11/10/13 06:52:23 0.00 0.0 / 0.0

edit: insert the @Mumak for first para only, since a post snug in between.