| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Server-aborted WUs |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Mysteron347
Senior Cruncher Australia Joined: Apr 28, 2007 Post Count: 179 Status: Offline Project Badges: 
|
CMD2_ 2299-2IAE_ B.clustersOccur-2OXE_ A.clustersOccur_ 64_ 35770_ 35818_ 0
was one of a number of WUs I had downloaded but were server-aborted. This particular WU had FOUR replications, each returning ERROR (and each returning ERROR very quickly, too) OK, I'm not worried by the fact that this particular WU has a problem. As for the other WUs, well - I don't know - problem, too, or simply a late reply making the processing redundant and hence aborting it (great!)?? What has me worried is that this unit is marked as 'in progress' as far as my 'my results' page is concerned. I would expect that the status would have been changed to 'server aborted' by the same process that issued the 'abort this WU' command/notification. Just seems a bit odd to me. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If the tasks has not yet cleared to report from your client that it was server aborted. BOINC servers wont presume that the result was aborted until the client confirms back... that's the process flow.
--//-- |
||
|
|
|