I've got the following Validate error and wonder what the cause of this is
as the Exit status is 0? Is it a false validation error?


Task 70745778
Name ps_separation_82_2s_mix4_1_71239_0
Workunit 47919032
Created 17 Jul 2011 | 18:29:30 UTC
Sent 17 Jul 2011 | 18:32:39 UTC
Received 17 Jul 2011 | 18:48:20 UTC
Server state Over
Outcome Validate error
Client state Done
Exit status 0 (0x0)
Computer ID 59862
Report deadline 29 Jul 2011 | 18:32:39 UTC
Run time 66.21
CPU time 3.35
Validate state Invalid
Credit 0.00
Application version MilkyWay@Home v0.82 (ati14)

Stderr output
<core_client_version>6.10.60</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>

And one more...

Task 70796862
Name ps_separation_17_3s_fix_2_1109740_0
Workunit 47951933
Created 17 Jul 2011 | 20:20:06 UTC
Sent 17 Jul 2011 | 20:24:50 UTC
Received 17 Jul 2011 | 20:41:39 UTC
Server state Over
Outcome Validate error
Client state Done
Exit status 0 (0x0)
Computer ID 59862
Report deadline 29 Jul 2011 | 20:24:50 UTC
Run time 132.52
CPU time 3.39
Validate state Invalid
Credit 0.00
Application version MilkyWay@Home v0.82 (ati14)

Stderr output
<core_client_version>6.10.60</core_client_version>
<![CDATA[
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Using SSE3 path
Found 2 CAL devices
Chose device 0

Device target: CAL_TARGET_CYPRESS
Revision: 2
CAL Version: 1.4.1332
Engine clock: 900 Mhz
Memory clock: 900 Mhz
GPU RAM: 1024
Wavefront size: 64
Double precision: CAL_TRUE
Compute shader: CAL_TRUE
Number SIMD: 20
Number shader engines: 2
Pitch alignment: 256
Surface alignment: 4096
Max size 2D: { 16384, 16384 }

Estimated iteration time 137.700694 ms
Target frequency 30.000000 Hz, polling mode 1
Dividing into 4 chunks, initially sleeping for 0 ms
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using 4 chunk(s) with sizes: 400 400 400 400

</stderr_txt>
]]>

Are that the complete stderr_txt? Because if yes, than of course this results are invalid, there is no result in them.

---

Yes it is but there was no 'Error while computing' so the question is was it caused by a bad wu or does my computer malfunktion?

I don't think it's a bad WU, the problem seem to be that the actuall result is not written to stderr.txt or like in the first case there was no stderr.txt at all (or it was empty), so yes, probably something on your end (if the wingmen has no problems, check that), but what it is... no idea.

---

Ok. Thank you Link.
It seams to happen rarely so it is no big deal I guess.
Just curious what the cause could be, maybe my HD which is rather old
on the box it happened.

This seems to happen some small percentage of the time. The end of stderr is just missing. It's some kind of BOINC bug.