Just got this one here.

This was on a MAC Dual G4 running MAC OS 10.4.6, BOINC 5.3.28

WU - NO_CHECK_7486h002_dec123_1.pdb_407_19_0

Looks like a file problem from this error message -

<message><file_xfer_error>
<file_name>NO_CHECK_7486h002_dec123_1.pdb_407_19_0_0</file_name>
<error_code>-161</error_code>
<error_message></error_message>
</file_xfer_error>

</message>

Well , I cannot find a bug reports thread to Linux 5.00
Thus, I am posting here !

This PC, 256 MB RAM, Pentium III 500 MHZ, has sucessfully completed this.
http://ralph.bakerlab.org/result.php?resultid=88940

Now it is crunching this WU, that appears stuck? at 1.14% - 2:57 Hours CPUtime
http://ralph.bakerlab.org/result.php?resultid=90223
However cause this PC is slooow ... I feel I should allow some more time
before reporting "stuck" -:!

Anyway, If 5.01 starts comming on, I will abort this result,
else, Ill allow more time to decide if it is really stuck,
or if is I that are impacient. !

[b]BTW: Wich debugger I need to Install on my Linux PCs ?[/b

So what sort of thing do you look for or notice in your testing (generally in beta testing)


Me I normally find the useability problems which should be easiest to sort out (though normally takes the longest to fix)

Then it'll be messing about with the new functions to see if the work or not.

What does irritate me the most is when people don't describe the problem in detail with some logs (which I do sometimes myself :s) to see if it can be reproduced.

The register page says that one can use the existing boinc account. But I can't attach to RALPH with my existing account and have to create a new one....

OK, I have just set that machine's "Leave in Memory" to YES. It has had 2/2 failures. Hopefully it'll get some more work soon.

I have another machine which has *always* had Leave in Memory set to YES return a good result. This one:

http://ralph.bakerlab.org/show_host_detail.php?hostid=81