Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Extended Sierpinski Problem :
Bad validations
Author |
Message |
|
Something in the Sierpinski ESP Sieve work unit validation needs to be beefed up. Host 438354 has plenty of error and inconclusive tasks, but also a lot which have been declared valid after a run time of less than 5 seconds. That can't be right. The most recent ones are dated July 25th, so maybe this has been stopped, but I wanted to point out that there are some bad double-checks (at least) out there.
--Gary | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13520 ID: 53948 Credit: 241,598,614 RAC: 307,859
                          
|
There's a problem there, yes. We're looking into it. Thanks.
____________
My lucky number is 75898524288+1 | |
|
JimB Honorary cruncher Send message
Joined: 4 Aug 11 Posts: 916 ID: 107307 Credit: 974,494,172 RAC: 1,227
                    
|
The problem should now be fixed. I'm not sure why I didn't make this change quite a while ago, actually. | |
|
|
I've been getting numerous errored out WUs, 90% on my AMD Phenom CPUs. Might there be a connection to this and the app it self? Looking at my WUs, only errors from today are showing so I guess past ones were slipping through the validation before this fix. But this still doesn't explain all the errors while computing. More errors (25+) on this since I started this sub project than all other CPU sub projects combined over the past year, so something is up with the PSP sieve app, at least for me.
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
| |
|
JimB Honorary cruncher Send message
Joined: 4 Aug 11 Posts: 916 ID: 107307 Credit: 974,494,172 RAC: 1,227
                    
|
Any sieving result affected by the validator change will show up with a status of "Validate Error". Those are listed with the invalid tasks. By definition this change is only going to affect jobs that didn't run long enough to yield a real result.
You have very few sieving errors, none of which would have been affected by the limited changes I made. in fact I'm not sure what you're looking at when you say 90% errored out on your AMD-based hosts.
Later edit: If you're clicking on the task and talking about "Factors file not found" that just means there were no factors in the p range you searched. That's not an error. | |
|
|
I have no inconclusive or invalids currently.
ESP-Sieve - All 1329 | In progress 306 | Pending 293 | Inconclusive | Valid 725 | Aborted | Invalid | Error 5
All my errors are while computing and never finish and reported by BOINC as Error While Computing. This happens at varying points in the WUs computation, anywhere from near the beginning to near the end time wise.
Edit: Those 5 errors from today where after a power outage earlier upon reboot.
I'm not sure what you're looking at when you say 90% errored out on your AMD-based hosts
I mean of those that errored out, 90% where on my 2 AMD computers and 10% where on my 2 Intel ones.
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
| |
|
Message boards :
Extended Sierpinski Problem :
Bad validations |