Today we started some new runs. These runs include:
de_separation_21_sSgr_1
de_separation_22_sSgr_1
ps_separation_21_sSgr_1
ps_separation_22_sSgr_2

If you notice anything strange with these runs please let me know. Thank you for your continued support!

Jake W.

de_separation_22_sSgr_1_
ps_separation_22_sSgr_1_
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>


[edit] added ps_separation_22_sSgr_1_ [/edit]

de_separation_22_sSgr_1_
ps_separation_22_sSgr_1_

First one works OK for me (on ATI HD3850 with the old 0.82 CAL app), second one I haven't had so far.

---

I have had two ps_separation_22_sSgr_1 units fail.

de_separation_22_sSgr_1_
ps_separation_22_sSgr_1_

First one works OK for me (on ATI HD3850 with the old 0.82 CAL app), second one I haven't had so far.

Update: no issues with both so far.

---

Had some de_separation_21_sSgr_1 and ps_separation_21_sSgr_1 fail also.

I will look into it and see whats going on. Thank you for getting back so quickly!

Jake W.

I had one fail today:

de_separation_22_sSgr_1_1358941502_19384205_0

Details: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=414701797

Yesterday everything ran fine. Today I can't get any tasks. Get this error message. Tried detaching and reattaching, same error.

3/8/2013 5:00:51 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/8/2013 5:00:51 PM | Milkyway@Home | Requesting new tasks for ATI
3/8/2013 5:00:52 PM | Milkyway@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
3/8/2013 5:00:52 PM | Milkyway@Home | [error] No close tag in scheduler reply

I found the problem. It's with the latest BOINC client 7.0.54. Went back to 7.0.52 and all is working again.

---

I had one fail today:

de_separation_22_sSgr_1_1358941502_19384205_0

Details: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=414701797

This one looks like it threw a NaN because it was searching a rough spot. Those should go away as the algorithm learns to stay away from there (probably has by now).

Had some de_separation_21_sSgr_1 and ps_separation_21_sSgr_1 fail also.

I can't find the failed work units - it looks like most of yours are succeeding without a problem, now. Let us know if you are still getting errors.

I found the problem. It's with the latest BOINC client 7.0.54. Went back to 7.0.52 and all is working again.

The BOINC developers have reproduced this, and confirmed it is likely a problem in the new BOINC client.

Had some de_separation_21_sSgr_1 and ps_separation_21_sSgr_1 fail also.

I can't find the failed work units - it looks like most of yours are succeeding without a problem, now. Let us know if you are still getting errors.

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=319796871

I have started to get a lot of `de_separation` errors

Error tasks page

All compleated work units fail with Too many errors (may have bug)

Got 1 error WU too.
WU 320835109
"Non-finite result
Failed to calculate likelihood"

I have started to get a lot of `de_separation` errors

Error tasks page

All compleated work units fail with Too many errors (may have bug)

most of the errors i'm getting right now are of that variety too...i also have a handful of errors that haven't yet been discarded server-side due to "too many errors (may have bug)." of those tasks, all of them have errored out on at least one wingman's computer and have already been distributed to a 3rd wingman, leading me to believe that these tasks will also soon be discarded server-side due to "too many errors (may have bug)."

Got 1 error WU too.
WU 320835109
"Non-finite result
Failed to calculate likelihood"

this is the error i see in the stderr ouputs of all my errored tasks as well.

strangely, errors seem to come in spurts on my machine. it'll go days, weeks, and sometimes even months without a single error or invalid task, but when they do show up, the show up in droves. i suppose that in the grand scheme of things i'm really not seeing that many errors (about 30 out of ~1500 per day, or ~2%), but that's a significant waste of compute power either way you look at it. no matter what changes i make to the hardware and/or software configs of this machine, it never seems to get rid of the errors, and so i always end up going back to the original hardware and software setups and wait it out...and sure enough, eventually the errors subside and my machine will run error free for some time. i hardly ever feel that the errors i see are due to host-side errors...not lately anyway.

---

Yesterday everything ran fine. Today I can't get any tasks. Get this error message. Tried detaching and reattaching, same error.

3/8/2013 5:00:51 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/8/2013 5:00:51 PM | Milkyway@Home | Requesting new tasks for ATI
3/8/2013 5:00:52 PM | Milkyway@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
3/8/2013 5:00:52 PM | Milkyway@Home | [error] No close tag in scheduler reply

I found the problem. It's with the latest BOINC client 7.0.54. Went back to 7.0.52 and all is working again.

There is a BOINC v7.0.55 available for download now (same place as you got v7.0.54 from). It's been released specifically to patch this problem - it would be good if somebody who hit the bug last time could test and report back.

IT IS WORKIIIIIIIIIIING !!! ....... :-)))

BOINC ver. 7.0.55 x64 is getting work from MilkyWay ! Yes!


See my computer called ELDEST here:
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=501866

Sorry if this is a dumb question but I don't know where to find the new 7.0.55 x64 version. Can someone please link it for me? Thank you!

Replying to a PM, on the basis that more than one person might be wondering...

The best place to pick up information about new downloads is

BOINC 7 Change Log and news

on the BOINC message boards. It has direct download links, and a brief note of the significant changes. Having said that, Ageless allows a few hours to pass before posting, just in case some dramatic error has slipped through the net.

v7.0.55 is there, and works, but still has a few cosmetic bugs. If you really want to live on the bleeding edge, you can pick up v7.0.56 from http://boinc.berkeley.edu/dl/?C=M;O=D - that has fewer cosmetic bugs, although I've already reported one that's been missed. If you download from that directory, you very much do so at your own risk.

[this is very much the same information as Mikey has already posted in Number Crunching, but copied here to link it with the original report of problems with v7.0.54]

Edit - v7.0.56 is now in the 'BOINC 7 Change Log and news' thread.