Are these only test units just to verify the validator? I've had 2 issues with them - Completed, validation inconclusive and when the consensus does come in, I get - Completed, can't validate due to the settings of - max # of error/total/success tasks 1, 6, 1 errors Too many success results

even worse - "Completed, can't validate" with zero credit. what the hell?

---

Something isn't working right....

See: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1644&nowrap=true#38053
Regards
Zy

IMO, the logic behind the "Too many error results, Too many total results" circuitbreaker and/or Milkway's "3, 6, 1" threshholding of it, is flawed. That is, once the "circuitbreaker" is triggered, any (as yet unreturned), "In progess" results appear to be excluded from consideration, despite the fact that they could be "valid". That doesn't make sense - especially on a project where only one valid result is required.

At least, that seems to be the case with ps_13_3s_const_v2_5688232_1269636198 and Task 95459389 (mine) which lists its "Validate state" as: "Workunit error - check skipped".

EDIT: Sorry - I didn't see the other thread until after I posted here.

Just checked my results. I have over 1000+ which have not validated.

Seems like about a 20% failure rate over the completed ones.
Also got heaps as inconclusive, so things might change as we go.

Travis is on to it, so things will work out in the end.

Regards

---

I suggest that "DB purging" be suspended until this "Too many errors . . ." problem is fixed. Else, a lot of work will be lost. The WU I reported (below) is already gone.

IMO, the logic behind the "Too many error results, Too many total results" circuitbreaker and/or Milkway's "3, 6, 1" threshholding of it, is flawed. That is, once the "circuitbreaker" is triggered, any (as yet unreturned), "In progess" results appear to be excluded from consideration, despite the fact that they could be "valid". That doesn't make sense - especially on a project where only one valid result is required.

At least, that seems to be the case with ps_13_3s_const_v2_5688232_1269636198 and Task 95459389 (mine) which lists its "Validate state" as: "Workunit error - check skipped".

EDIT: Sorry - I didn't see the other thread until after I posted here.

I am getting a lot of these..

DD,

<core_client_version>6.10.36</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home ATI GPU application version 0.20b (Win64, CAL 1.4) by Gipsel
ignoring unknown input argument in app_info.xml: -np
ignoring unknown input argument in app_info.xml: 20
ignoring unknown input argument in app_info.xml: -p
ignoring unknown input argument in app_info.xml: 0.8131935629570660000000000
ignoring unknown input argument in app_info.xml: 8.5161548212469430000000000
ignoring unknown input argument in app_info.xml: -1.1780421318022150000000000
ignoring unknown input argument in app_info.xml: 170.3258800342236400000000000
ignoring unknown input argument in app_info.xml: 22.4470822186396650000000000
ignoring unknown input argument in app_info.xml: 0.2629632502059480000000000
ignoring unknown input argument in app_info.xml: 6.0421462150014010000000000
ignoring unknown input argument in app_info.xml: 4.6010011677850150000000000
ignoring unknown input argument in app_info.xml: -1.5756575205385368000000000
ignoring unknown input argument in app_info.xml: 154.8731425030765000000000000
ignoring unknown input argument in app_info.xml: 18.4402261956227560000000000
ignoring unknown input argument in app_info.xml: 4.0265024652404140000000000
ignoring unknown input argument in app_info.xml: 5.0916863847601270000000000
ignoring unknown input argument in app_info.xml: 19.6568110079780500000000000
ignoring unknown input argument in app_info.xml: -16.8451942358860260000000000
ignoring unknown input argument in app_info.xml: 230.0931547168204600000000000
ignoring unknown input argument in app_info.xml: 31.7470334331690330000000000
ignoring unknown input argument in app_info.xml: 0.0000000000000000000000000
ignoring unknown input argument in app_info.xml: 0.0000000000000000000000000
ignoring unknown input argument in app_info.xml: 17.0962754025640400000000000
instructed by BOINC client to use device 0
CPU: AMD Phenom(tm) 9600 Quad-Core Processor (4 cores/threads) 2.30012 GHz (342ms)

CAL Runtime: 1.4.515
Found 1 CAL device

Device 0: ATI Radeon HD4700/4800 (RV740/RV770) 512 MB local RAM (remote 64 MB cached + 1024 MB uncached)
GPU core clock: 765 MHz, memory clock: 950 MHz
800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

Starting WU on GPU 0

main integral, 640 iterations
predicted runtime per iteration is 275 ms (33.3333 ms are allowed), dividing each iteration in 9 parts
borders of the domains at 0 184 360 536 712 888 1072 1248 1424 1600
Calculated about 3.28897e+013 floatingpoint ops on GPU, 2.47165e+008 on FPU. Approximate GPU time 184.781 seconds.

probability calculation (stars)
Calculated about 3.34818e+009 floatingpoint ops on FPU.

WU completed.
CPU time: 8.39063 seconds, GPU time: 184.781 seconds, wall clock time: 186.542 seconds, CPU frequency: 2.30016 GHz

</stderr_txt>
]]>

Validate state Initial
Claimed credit 0.846776257001705
Granted credit 0
application version MilkyWay@Home v0.21 (ati13ati)

---