Task was reported too late to validate
Joined: 7 Dec 10
Hello - I have a couple of 16 processor machines running Linux working on E@home. From time to time I get these weird errors where it says that 'task was reported too late to validate' although I'm under the time limit for the work unit. From the stderr output I think the client is generating output that the server validator can't handle. Stderr output below:
wrapper: running ../../projects/www.enigmaathome.net/enigma2_0.76_i686-pc-linux-gnu (-R -o results.txt 00trigr.cur 00bigr.cur 00ciphertext)
2011-01-04 11:23:11 enigma: working on range ...
2011-01-04 12:09:45 enigma: finished range
Validator debug: started 20664798
Validator info: received file was in wrong format or incomplete.
debug: read = M3=B:125:AA:AAA=B:125:ZZ:ZZZ=B:125:ZZ:ZZZ=2=0=0=2147483646
Here's the task url:
Any help would be appreciated - I'm running the current client, not the development version on Centos 5.
Joined: 8 Jan 11
Hi - I am having the same issue.
Please take a look at this work unit:
It was returned within 3h but was reported as "too late to validate".
I am also running the latest stable client and other work units get validated just fine.
Joined: 26 Nov 07
Hi- same problem , 0 Points.
Joined: 25 Aug 07
These results are not too late, but invalid. Validator debug/info (as seen at results page, bottom section of stderr) says that something is wrong with the output file, usually an error like that suggests that the file was just incomplete. The question is, what caused the problem.
The validator sets wrong flags for invalid results, that's why it's listed as "too late" instead of "invalid". I used this flag for tests and as a workaround for transitioner bug and forgot to change it back.
M4 Project homepage
M4 Project wiki