X-Files 27, I can do better than that - 4d, 11+ hours, and still going...

FWIW It seems that if you have a unit @ 100% and no check points it's a dud. I had several earlier that never finished and wouldn't restart.

@gb009761: How many other tasks could you have finished in the 4+ days that you've put into that 1 task? Just sayin.

nanoprobe, as it's my electric that I'm using, and for the sake of testing/proving that these don't ever appear to finish (just think of the WU's that are sent to "unmonitored" BOINC sessions - after all, the "set and forget" brigade are far larger than those who are active on the forums), I am willing to forgo a few "wasted cycles" if it helps the techs in the long run find out what's going wrong with these.

Just to expand upon the issue, the WU that I've got which appears stuck, currently has 4 copies "out in the wild", 3 * "no reply" (which, I'm assuming, the other two besides mine, could still be running - i.e., "wasting" cycles), and another WU "in process" - which, again, will probably also go the same way. Thus, if I can help the techs, then I will. After all, if no one highlights these/is willing to see as to whether they'll ever finish if they're just left to run, then who knows as to how many cycles would be wasted through the life of this particular project. I'm not here to try and crunch through as many of the WU's as possible, I'm here for the long-term good of the project.

Well, due to a "No heartbeat from client for 30 sec - exiting" issue, my WU reset itself, again, going straight to 100% complete and again, having the CPU/Elapsed time continuing to increment.

What I am surprised about though, is this line from the messages tab I would have thought that BOINC would have killed it - but no, it's left for human intervention to kill it (which I'm just about to do so - I have made a copy of the relevant slot for the techs benefit, if they want anything from out of there).

If it is left up to the person running BOINC to spot it and kill it manually (like it certainly looks like), then that further convinces me that those other 3 WU's (2 * "No Reply" and 1 * "In Progress"), will continue indefinitely - thus, making this something the techs may seriously want to investigate...

Hi Lawrence, that's why I've already e-mailed all the details I believe they'll need through to the techs (as can be seen from my previous posts, I did that yesterday).

As to "These problems are normal at the start of a project", that's why I'm highlighting it for the techs now - whilst we're in the "pre-official announcement, production testing" stage. If (and I'm most certainly not saying that this is - it's not my judgement to call), this is some sort of major issue, then it's best to get it resolved before the project is officially launched.

With regards to BOINC eventually killing overdue WU's, I sincerely hope that, eventually, it would have killed them. What I was slightly surprised about, was that it hadn't killed it after being 4.75 days overdue (anyone know what the actual time limit is?).