For my machine, from what I can tell, I've had only ONE Inconclusive out of 1,253 work units for this project.

If you fetched them before the outage and were circulate as single they would go inconclusive at this time. Those new tasks circulated after the outage I'd venture to think are up front quorum 2 and pass via Pending Validation for whoever returned the result first in the quorum. Maybe knreed has enough data by Friday to start the reliability ratings functions again and we're allowed to do it mostly alone again for FAAH/HFCC/C4CW/CEP2 (4 sciences I count that have zero redundancy).

This of course is separate from the quorum 2 where the results are enough dissimilar to warrant a third opinion.

--//--

OK... so all devices are considered unreliable until they can prove to be reliable. I tried to understand the humungous reliability table in the FAQ, but wasn't very successful in making heads or tails of it (and will take SekeRob's resume of what is required). I assume that at some point in history my devices will become reliable again. Now for the question:

- Does "Server Aborted" count as a strike against becoming reliable again?

I just had one of my C4CW WUs show up as "Server Aborted" this morning. I hope not it won't be counted against me since it wasn't my fault (I could go on about why I think this error shouldn't even exist, but will leave it for another day).

Thanks,

CJSL

Fail to see what badly overestimated run time task, see https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,32772 , has anything to do with inconclusive tasks, but anyway, you've aborted the task [an emergency manager action ;-]. The task would have completed in normal time.

CJSL,

The Server Aborted tasks go against daily quota [when max, 80 per core per day], not against relialibity.

--//--

SekeRob... thanks for the reply/answer.

CJSL