Crystal Pellet's comment might explain why I saw a message in the log about a task that wouldn't finish it time. I couldn't see why I might get that, but if it was a beta unit that was not being downloaded to a slow machine then that would make sense.

I quite understand the need to get fast results from the beta, but hope that this might be tweaked to be a little more forgiving in production.

I agree, but just wanted to make the point.

In fact, one could argue that the beta is not, in fact, testing the production scenario accurately for this very reason. I would hate to find that slow machines cause the system problems, once the deadline is extended.

I got two of them with the same error.

Result Log

Result Name: FAH2_ 9999984_ avx38789_ 000001_ 000539_ 021_ 0--
<core_client_version>7.0.27</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>wcgrid_beta21_bedam_7.18_x86_64-pc-linux-gnu</file_name>
<error_code>-120</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>

Result Name: FAH2_ 9999984_ avx38789_ 000001_ 000863_ 018_ 0--
<core_client_version>7.0.27</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>wcgrid_beta21_bedam_7.18_x86_64-pc-linux-gnu</file_name>
<error_code>-120</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>

Both items are from a machine on a wireless link. Other machines on the same wireless link have successfully downloaded and processed beta work units.
Cheers

Hello everyone,

The beta test is still currently on going. We are going to discuss with the researchers to see if they wish to have these results continue to get more data back or if they have enough to look at production fahb workunits only.

Thank you again for your participation in beta, hopefully a few of you were able to get a new badge :)

Thanks,
-Uplinger

I received another 3 long runners with 50,000 steps (9999986's) on a slow machine (1 thread idle) and not being able to return on time.
Estimated 24.5 - 25 CPU-hours, so only a bit late, but initiating 3 resends.
The machine in question: Intel Atom CPU Z3735F 1.33GHz

Maybe the deadline for tasks with more than 30,000 steps can be increased for this beta test and for the production FAH2 batches with the 50k steps.