My computer (http://moowrap.net/show_host_detail.php?hostid=166) with an ATI HD5850 is receiving computation errors on all workunits it attempts to download. I tried resetting the project, closing BOINC removing the project folder from All Users\Application Data\BOINC\projects and letting BOINC d/l new files, etc and still no luck. This has to be something with the application because my computer worked just fine before last weekend.

Same here on this host- Host 193 Ran fine for a week or so, been erroring out all wu's for the past few days. XP64 OS

Hi,

Interesting, seems to be a bug in checkpoint interval calculation. Maybe related to v6.10.18 client. I'll investigate and hopefully fix for next application version due soon.

Thanks for bringing this to my attention!

-w

thanks, Teemu. Indeed, it appears to be the BOINC version 6.10.18, upgrading to 6.10.60 fixed my issue.

Hi,

I investigated this and the only viable solution was to bump our required BOINC Client to v6.10.22 that has the feature my wrapper needs. Hopefully that's not too invasive change for people given this version was released 17 months ago and previously required v6.10.17 was released 19 months ago. :)

-w

There is a reason why I use the 6.10.18. An old scheduler bug that seems the developer can't reproduce that cause start and stop of many WUs with slightly wrong deadline date order. This cause many WUs go to "waiting to run" state, increasing the probability (on critical deadline projects WU queue) that the incomplete WUs go out of the deadline.

So running BOINC release > 6.10.18 may cause a waste of CPU time or a waste of my time, tuning the queue ;)
I'll try to update BOINC only on my PC with ATI GPU, using on it not deadline critical CPU projects ...

This cause many WUs go to "waiting to run" state, increasing the probability (on critical deadline projects WU queue) that the incomplete WUs go out of the deadline

Ah, interesting. I've seen this "multiple waiting to run" too and it seems to happen when there are high priority jobs due to BOINC Client thinking they will miss deadline. (Which was not case but happened due to switching to anonymous platform without flops.)

Bad news is that I saw this on v6.12.19, but I haven't run the latest stable v6.12.26 long enough to see if it still happens or if it got finally fixed. Probably not, if developers can't reproduce. :(

-w