Questions and Answers :
GPU applications :
Bugreport: boinc reported success but has failed
Message board moderation
Author | Message |
---|---|
juko Send message Joined: 27 Feb 10 Posts: 1 Credit: 45,560 RAC: 0 |
Hello, I have seen it twice, that boinc has reported a successfull outcome. But stderr output looks like this:
The above doesn't look like an successfull run. My question is, what happens if two machines with the same bug compute the same workunit? In a bad case they deliver both the same false result. And the validation process can't detect it. Is this correct? Greetings Juergen |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
Absolutely normal - no error SETI@Home Informational message -9 result_overflow Means - the WU is considered too noisy if too many "signals" are found and after max 30 "signals" of one kind is aborted by purpose/design by SETI@Home app, not by BOINC Credit is given for the effort (time, FLOPS) till abort e.g. if the WU processing is discontinued after 77% - then about 77% of the credit for the full to-the-end computation is given . Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
If you see this happening in multiple WU's then you probably need to restart. Sometimes the GPU gets glitchy or overheats and starts throwing bad results out. In that case just restart your computer In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.