Just saw an odd thing happen in the client (GUI). It started working on this WU:

21se03ab.25606.2416.540910.168_2

And completely finished it 1 minute 46 seconds later (says Ready to report now).

Corrupt WU? Its gone already of course so I can't peek at it. The log didn't say it was corrupt (no errors at all logged, looked like it transferred just fine too, except it tacked on another _0 to the filename) - i.e. this is what the Messages tab shows for the uploading of the completed work:

SETI@home - 2004-07-11 19:32:48 - Starting computation for result 21se03ab.25606.2416.540910.168_2 using setiathome version 3.08
SETI@home - 2004-07-11 19:32:48 - Started upload of 11ja04aa.1511.14546.61078.222_0_0
SETI@home - 2004-07-11 19:32:55 - Finished upload of 11ja04aa.1511.14546.61078.222_0_0
SETI@home - 2004-07-11 19:32:55 - Approximate throughput 6742.937940 bytes/sec
SETI@home - 2004-07-11 19:33:17 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-11 19:33:21 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-11 19:33:21 - Project prefs: no separate prefs for home; using your defaults

SETI@home - 2004-07-11 19:34:37 - Computation for result 21se03ab.25606.2416.540910.168 finished
SETI@home - 2004-07-11 19:34:37 - Starting computation for result 11ja04aa.1511.14546.61078.82_2 using setiathome version 3.08
SETI@home - 2004-07-11 19:34:37 - Started upload of 21se03ab.25606.2416.540910.168_2_0
SETI@home - 2004-07-11 19:34:44 - Finished upload of 21se03ab.25606.2416.540910.168_2_0
SETI@home - 2004-07-11 19:34:44 - Approximate throughput 6378.468086 bytes/sec

I had yesterday 2 WU's with very short CPU time: 1 min and 3 seconds and another of 2 minutes and 13 seconds.
For these WU's we had in the Beta test phase a message that came up.

Anyway, the reason why it has a short CPU time as due to the fact the number of results that are detected is exceeding the storage space allocated. This could be due to a radio signal source from earth disturbing the signals of the WU itself.

If you are using BoincView, you will find the reason for this very short CPU time in the corresponding xxxxxx.log.xml file under stderr_txt.

You can also find the same message, which is "SETI@Home Informational message -9 result_overflow NOTE: The number of results detected exceeds the storage space allocated", in the client_state.xml or in the sched_request.xml under the Boinc folder.

Typical for these WU's is they contain signals that are quite high in amplitude.

Greetings from Belgium.

Yea i had a few short WUs. One was 1minute exactly another as 1 minute 30 seconds. So it might have been SETI sending some test WU :s

Thank you for the responses Thierry and Jaaku, both sound like what I saw in the post above.

.