On 12/24/09, David Anderson <[email protected]> wrote:
> The server tells the client to abort a result only when
> 1) the result isn't in the DB
> 2) the result's WU was cancelled.
> In either case, it writes a string of the form
> "[HOST#%d]: Send result_abort for result %s; reason: %s\n"
> to the scheduler log.
>
> So scan your scheduler log and see if you're getting any of these.
But did the server tell the client to abort? From the output of
result.php, we can't know if the result was aborted or not, because:
There is a bug in the PHP code when creating the 'state' text, in
result.inc after line 125.
if ($result->exit_status == -221) { return "Redundant result"; }
Later, if $result->client_state is 6, it checks exit_status against
-221 again (line 134), returning "Cancelled by server". However, at
that point it's impossible for exit_status to be -221. If it was, the
function would have already returned in the previous if. So we'll
never get to see the web say "Cancelled by server"
--
Nicolas
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
