An old BOINC bug, it sends out results that wouldn't ever have had a chance to be valid, caused by the limits :

max # of error/total/success tasks 3, 10, 6

Especially with the long running ones, the error limit is too low.

I have one with wingmen errors :

Not started by deadline - canceled
Aborted by user
Error while computing (an unreliable box that has ~1/3rd errors)
Completed, can't validate (mine *sigh*)
Error while computing (ERR_RESULT_START, result not even started)
Error while downloading (ERR_RESULT_DOWNLOAD)

None of the errors is caused by the result itself but still it is invalid

http://universeathome.pl/universe/workunit.php?wuid=2850372

The other one looks very similar.

http://universeathome.pl/universe/workunit.php?wuid=2850252


I aborted three now (_5 and _6) because the risk to waste a lot of CPU time is much too high with those settings.

p.s.: The _6 results are always doomed, if a workunit had nothing but error results so far. BOINC still sends one out (this is the ancient BOINC server side bug)

p.p.s.: A second really old BOINC bug is that hosts with only 2% valid results still can have the full quota, reported a lot of times, but in Berkeley no one cares.

I have 14,81% of errors and I also think I waste CPU time for this project.

I have 14,81% of errors and I also think I waste CPU time for this project.

I see that one of your computers have a problem with errors. On other one you have some cancelled WU's because some tasks not finished on time (or not started).

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Było kilka zadań, które miały deadline tego samego dnia, w którym zostały pobrane. Z tego powodu anulowałem inne. Raz też miałem zadania, które resetowały się po każdym uruchomieniu. Jednak trzeba przyznać, że jest sporo zadań, które się kończą błędem. Wcześniej to się praktycznie nie zdarzało, podobnie w innych projektach.

I don't want to be misunderstood. My point was not that I think that the application is faulty in any way.

I just think that the error quota should be increased, as a lot of hosts seem to have trouble with things that are not connected to the application itself.

With the current setting, the risk is (too) high that a successful result doesn't make it into the science database