Please take a look at this WU: http://setiweb.ssl.berkeley.edu/workunit.php?wuid=10747183
You'll see that 2 hosts have completed the WU (needing >10000 and >14000 seconds) but one aborted it after ~300 seconds and the validator classified this result as invalid, but granted credit for the two other results.
That means that the result of this WU has been accepted with only 2 valid results.
Shouldn't it rather have said something like "Checked, but no consensus yet" and wait for the fourth host to return its result?

---

> Please take a look at this WU:
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=10747183
> You'll see that 2 hosts have completed the WU (needing >10000 and >14000
> seconds) but one aborted it after ~300 seconds and the validator classified
> this result as invalid, but granted credit for the two other results.
> That means that the result of this WU has been accepted with only 2 valid
> results.
> Shouldn't it rather have said something like "Checked, but no consensus yet"
> and wait for the fourth host to return its result?
>
Berkeley could have changed it back to 2 returned results to clear some of the backlog, so they can do more work on the database.

---

> Please take a look at this WU:
> http://setiweb.ssl.berkeley.edu/workunit.php?wuid=10747183
> You'll see that 2 hosts have completed the WU (needing >10000 and >14000
> seconds) but one aborted it after ~300 seconds and the validator classified
> this result as invalid, but granted credit for the two other results.
> That means that the result of this WU has been accepted with only 2 valid
> results.
> Shouldn't it rather have said something like "Checked, but no consensus yet"
> and wait for the fourth host to return its result?
>

A seti-wu isn't for the moment tried validated before got atleast 3 "success"-results reported, but the seti-validator is programmed in such a way that it's possible the wu is validated with only 2 of the results passing validation.