Hi Michael,
I checked out the result in question, and this is what the stderr said:
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.
Check out the other returned results for this WU:
http://setiathome.berkeley.edu/workunit.php?wuid=124512405They also show a -9 result overflow error.
So it wasn't a computational error, but rather a signal overflow (which is normal and should be ignored). Most noisy WUs reach this threshold very quickly, some take quite a bit of time. It seems that the optimized apps produce different result files than the stock app sometimes when they error out in this way; I'd put it down to Karma, or better yet, blame Misfit
HTH,
Simon.