Advanced search

Forums : Wish list : result_abort_if_not_started / result_abort
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Mr.Pernod
Avatar

Send message
Joined: 15 Jul 07
Posts: 60
Credit: 841,431
RAC: 0
Message 1316 - Posted: 21 Jul 2007, 15:22:10 UTC

I think it would make the mass-cancellation of "faulty" workunits (like juli 20/21) a lot less stressfull if the <send_result_abort> option was enabled in the scheduler for this project.
The project-admins would only have to batch-cancel the work serverside and the (most recent) BOINC clients would take care of the rest on the users computers.
For people with older clients it would still mean a manual check/cancel unfortunately.

3165 3165         browser.C  
3166 3166         prefs.C  
     3167   
     3168   David  5 Apr 2007  
     3169     - Scheduler: add option <send_result_abort>. If set:  
     3170       - If client is processing a result for a WU that has  
     3171         been cancelled or is not in the DB  
     3172         (i.e. there's no chance of getting credit)  
     3173         send <result_abort>.  
     3174       - If client is processing a result for a WU that has  
     3175         been assimilated or is overdue  
     3176         (i.e. there's a chance of not getting credit)  
     3177         send <result_abort_if_not_started>


Changeset 12322 - BOINC - Trac

Both SETI and SETI-beta are using the option and it seems to work quite nicely.
ID: 1316 · Report as offensive     Reply Quote
Profile Scott
Volunteer moderator
Project administrator
Project developer
Avatar

Send message
Joined: 1 Apr 07
Posts: 662
Credit: 13,742
RAC: 0
Message 1419 - Posted: 23 Jul 2007, 14:28:08 UTC - in response to Message 1316.  

I think it would make the mass-cancellation of "faulty" workunits (like juli 20/21) a lot less stressfull if the option was enabled in the scheduler for this project.
The project-admins would only have to batch-cancel the work serverside and the (most recent) BOINC clients would take care of the rest on the users computers.
For people with older clients it would still mean a manual check/cancel unfortunately.

3165 3165         browser.C  
3166 3166         prefs.C  
     3167   
     3168   David  5 Apr 2007  
     3169     - Scheduler: add option <send_result_abort>. If set:  
     3170       - If client is processing a result for a WU that has  
     3171         been cancelled or is not in the DB  
     3172         (i.e. there's no chance of getting credit)  
     3173         send <result_abort>.  
     3174       - If client is processing a result for a WU that has  
     3175         been assimilated or is overdue  
     3176         (i.e. there's a chance of not getting credit)  
     3177         send <result_abort_if_not_started>


Changeset 12322 - BOINC - Trac

Both SETI and SETI-beta are using the option and it seems to work quite nicely.

Sorry I didn't get back to you sooner, but I emabled in the project configuration file on Saturday night. I just now cancelled the rest of the bad WUs, so we should be good now.

Thanks for the suggestion.
Scott Kruger
Project Administrator, Cosmology@Home
ID: 1419 · Report as offensive     Reply Quote
Profile Mr.Pernod
Avatar

Send message
Joined: 15 Jul 07
Posts: 60
Credit: 841,431
RAC: 0
Message 1424 - Posted: 23 Jul 2007, 14:44:17 UTC

sweet.

now to get everybody to upgrade to the latest BOINC client-version ;-)
ID: 1424 · Report as offensive     Reply Quote
Profile Bryan Siegfried
Avatar

Send message
Joined: 8 Jul 07
Posts: 26
Credit: 3,740,940
RAC: 0
Message 1452 - Posted: 23 Jul 2007, 22:43:28 UTC - in response to Message 1424.  

sweet.

now to get everybody to upgrade to the latest BOINC client-version ;-)


Will <send_result_abort> not work with 5.8.x? I am not looking forward to changing the set-up on all my linux boxen. To date, I have been able to rely on the packages in the ubuntu repos....
Computers are useless. They can only give you answers. (Pablo Picasso)
ID: 1452 · Report as offensive     Reply Quote
Profile [B^S] Acmefrog
Volunteer tester
Avatar

Send message
Joined: 8 Jun 07
Posts: 175
Credit: 446,074
RAC: 0
Message 1453 - Posted: 23 Jul 2007, 22:47:59 UTC - in response to Message 1452.  

sweet.

now to get everybody to upgrade to the latest BOINC client-version ;-)


Will <send_result_abort> not work with 5.8.x? I am not looking forward to changing the set-up on all my linux boxen. To date, I have been able to rely on the packages in the ubuntu repos....


I believe it should work. My other pc is running 5.8.16 and it automatically aborted several. The pc obviously had to contact cosmo to d/l the instructions.
ID: 1453 · Report as offensive     Reply Quote
Profile teemac
Avatar

Send message
Joined: 3 Jul 07
Posts: 13
Credit: 749,995
RAC: 0
Message 1456 - Posted: 24 Jul 2007, 2:48:32 UTC

4 of my boxes run Linux and Boinc 5.8.17 and had no trouble receiving the 'abort' message automatically from Cosmo.
ID: 1456 · Report as offensive     Reply Quote
=Lupus=

Send message
Joined: 22 Jun 07
Posts: 2
Credit: 152,441
RAC: 0
Message 1459 - Posted: 24 Jul 2007, 8:59:30 UTC

Yeah worked on the last "faulty" one for me (cc 5.8.16)... Thanks.
ID: 1459 · Report as offensive     Reply Quote

Forums : Wish list : result_abort_if_not_started / result_abort