Verified experimentally - I wasn't convinced. I suspended networking, suspended a task, and gave it an artificially short deadline.
19/04/2011 09:06:38 | | Suspending network activity - user request 19/04/2011 09:34:19 | SETI@home | Computation for task 24no10ab.5400.4329.12.10.90_1 finished 19/04/2011 09:34:19 | SETI@home | Starting 24no10ab.5400.4329.12.10.89_0 19/04/2011 09:34:19 | SETI@home | [cpu_sched] Starting 24no10ab.5400.4329.12.10.89_0 (initial) 19/04/2011 09:34:19 | SETI@home | Starting task 24no10ab.5400.4329.12.10.89_0 using setiathome_enhanced version 610 19/04/2011 09:50:48 | SETI@home | Aborting task 07mr11aa.13982.16836.10.10.59_2; not started and deadline has passed 19/04/2011 10:01:34 | SETI@home | Computation for task 24no10ab.5400.4329.12.10.89_0 finished 19/04/2011 10:01:34 | SETI@home | Starting 24no10ab.5400.4329.12.10.101_0 Task showed in BOINC Manager as "Aborted: not started by deadline" http://img715.imageshack.us/img715/5849/abortednotstarted.png When viewed on the website, it appears with Client state Aborted by user Exit status -233 (0xffffffffffffff17) - that might help with Bernd's original question http://setiathome.berkeley.edu/result.php?resultid=1874372348 ----- Original Message ----- From: "Richard Haselgrove" <[email protected]> To: "David Anderson" <[email protected]>; <[email protected]> Sent: Monday, April 18, 2011 11:59 PM Subject: Re: [boinc_dev] Aborted (by user)? > My apologies - I gave Bernd that impression on the strength of > http://boinc.berkeley.edu/trac/changeset/17399 > > and lines 1143-1158 of the current (trunk) client_state.cpp > > Changeset 17399 contains > #define ERR_UNSTARTED_LATE -233 > > which again appears in current code, but appears not to be listed on that > Wiki page. > > > >> Actually the client doesn't make the decision to abort tasks; >> it's instructed to do so by the scheduler. >> >> It's possible to discriminate most cases: see >> http://boinc.berkeley.edu/trac/wiki/JobStatus >> >> -- David >> >> On 18-Apr-2011 1:29 AM, Bernd Machenschalk wrote: >>> HI! >>> >>> I recently learned that newer clients automatically abort tasks that have >>> not >>> been started and are already past the deadline. I like this better than >>> the >>> previous "... consider aborting it" message. However this is something >>> the >>> user has no control about. So the text "aborted by user" at various >>> places >>> (at least in the web code) is outdated and somewhat misleading. >>> >>> Additionally I, as a project manager, would really like to know whether a >>> task was aborted by the client because it passed the deadline (which >>> might >>> suggest an extension of the deadlines), or whether it was aborted >>> manually >>> for other reasons. Is there a way to distinguish these two cases? If not, >>> could there be made one e.g. by using a different exit status? The way >>> the >>> web code should be updated / fixed would clearly depends on whether these >>> cases can be distinguished. >>> >>> Best, Bernd >>> >>> _______________________________________________ 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. >> _______________________________________________ >> 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. >> > > > _______________________________________________ > 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. > _______________________________________________ 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.
