I doubt that your result is faulty, I rather think that
the validator - the server side program that compares
the results of one workunit against eachother - has a flaw.
Just had a WU not validate which I had crunched running XP. The other two hosts were Linux and Darwin, and those two seemed to agree with each other but not with me. This box is NOT overclocked (how should it be, it's a notebook) and normally returns perfectly valid results, so it might be the validator again.
And a 524-credit-WU, too. I got relatively lucky at the beginning of the run, but now I seem to be collecting computation errors and invalid results like anyone else, plus getting hell from a beta app which REALLY doesn't seem to like my desktop box...
Yeah well, life is hard ;-) I'm sure things will work out soon enough.
Why is this WU invalid?
)
Because you have Windows and the other two are Linux
results.
Just today someone posted more WUs in our team forum
that didn't validate between Linux and Windows
(checked but no consensus yet)
All were pre-4.17 results though, maybe they have fixed
it with 4.17
My Millenium machines
)
My Millenium machines validate against Linux with the 4.13 (for Windows) and the 4.14 (for Linux).
Dual Core AMD Opteron 185 - Linux 2.6.17-hexe-smp
Xeon 2.66GHz - Linux 2.6.17-1.2143_FC4smp
Celeron 2.00GHz - Linux 2.4.18-5
[
RE: Because you have
)
Well, in fact I use MacOS X on a PowerMac G5 and client version 5.8.17. My result is the 0.00 credit, NOT the computation error one.
RE: RE: Because you have
)
The WU you listed is for your Pentium D machine.
RE: RE: Because you have
)
I see no 0.00 credit on your Macs.
The only 0.00 credit is with your Pentium D.
[
RE: I see no 0.00 credit
)
Sorry, you are right!
I have received zero points
)
I have received zero points for this one. I'm running linux, the others xp and vista. Any thoughts on the reason my result was invalid?
TIA,
Bert
Somnio ergo sum
I doubt that your result is
)
I doubt that your result is faulty, I rather think that
the validator - the server side program that compares
the results of one workunit against eachother - has a flaw.
Same thing happened to me.
)
Same thing happened to me. See the thread on WHY No Credit? I think we are getting a kick in the behind.
Just had a WU not validate
)
Just had a WU not validate which I had crunched running XP. The other two hosts were Linux and Darwin, and those two seemed to agree with each other but not with me. This box is NOT overclocked (how should it be, it's a notebook) and normally returns perfectly valid results, so it might be the validator again.
And a 524-credit-WU, too. I got relatively lucky at the beginning of the run, but now I seem to be collecting computation errors and invalid results like anyone else, plus getting hell from a beta app which REALLY doesn't seem to like my desktop box...
Yeah well, life is hard ;-) I'm sure things will work out soon enough.