There are lots of validate errors appearing among recently processed TRP-Sieve WUs. For example, host 523834 had more than a thousand validate errors over the last couple of days.

Among its valid tasks are only tasks with a factor found or validated before the afternoon of January 7, so maybe this was broken when Jim changed the validator to deal with somehow corrupted output files.
____________

There are lots of validate errors appearing among recently processed TRP-Sieve WUs. For example, host 523834 had more than a thousand validate errors over the last couple of days.

Among its valid tasks are only tasks with a factor found or validated before the afternoon of January 7, so maybe this was broken when Jim changed the validator to deal with somehow corrupted output files.

Fixed. It wasn't what I thought. I had made changes in the way upload files were read and had neglected to account for every possible situation. All TRP Sieve workunits have been revalidated and there aren't any of them with validate errors any more. A validate error generally means that there's something wrong with the result itself. In this case the uploads were not being read at all and the validator considered them to be missing.

Thank you, Patrick, for pointing that out.

I found two tasks marked as valid but it looks like they have not be completed. 785641742 and 785616758
____________
144052 *5^2018290+1 is Prime!

I found two tasks marked as valid but it looks like they have not be completed. 785641742 and 785616758