Maybe one of you here has an idea… #boinc on Freenode
was rather clueless.

Sometimes, I have WUs at fraction done 1.000000 that
don’t finish. Playing with client_state.xml let them
finish but not upload, so reporting yields an error.

Is there a way to manually tell the core client that
WU x has finished (e.g. if reading slots/*/stderr.txt
shows that it’s clearly done), so that it uploads and
then marks the WU as ready to report?

I had this issue with:
• WCG (1 hanging, 1 valid, 3-4 invalid (testing))
• Sztaki Desktop Grid (3-4 hanging, a dozen valid)
• Sudoku (1 hanging, a dozen valid)
• Spinhenge (3-4 hanging, two or three dozen valid)
I didn’t yet see it with other projects.

Sometimes, hanging WUs finish after a day or two,
where the app doesn’t use up any CPU at all if the
project’s at turn. (Add a few --quits and restarts
of the core client to some of these occurences.)
Sometimes, worse, hanging WUs restart from the begin-
ning after a day or two, and then (usually) finish
right after computing is done (result is valid, ex-
cept once, when it returned the concatenation of two
valid results, which wasn’t properly truncated and
thusly yielded a computation error).

Playing with client_state.xml let them
finish but not upload, so reporting yields an error.

Is there a way to manually tell the core client that
WU x has finished (e.g. if reading slots/*/stderr.txt
shows that it’s clearly done), so that it uploads and
then marks the WU as ready to report?

mirabilos wrote:

Playing with client_state.xml let them
finish but not upload, so reporting yields an error.

Come again? How do you 'play' client_state.xml?

Mind posting messages from the Messages log to show what happens on your system?

And can you please register at the BOINC Dev forums and repost it there? If it needs developer attention, it's easier to do it through there than through here.