On the 'credit' side of the situation: remember that CPDN awards credit incrementally, as each trickle is reported. Those interim credits would NOT be taken away if either you or the project aborted the task early - the only 'wasted' computation time would be that from the time of the final trickle to the time of the abort. You could wait until a tickle was reported, and abort the task immediately afterwards - wasting practically nothing.

As expected, the other user has finished the tasks I got due to a time-out. However, I still have the tasks and they show as In Progress. I'd have expected for the server to cancel them, like Rosetta does, in situations like this. How does CPDN handle such cases? Do I have to abort them myself?

I checked with Andy about this. CPDN doesn't issue a 'not needed' response if a earlier task in the workunit finishes. Experience has taught them users get annoyed by tasks being killed. So, yes, you'll need to abort it yourself.

Thank you for checking. I'll abort those 5 tasks. Luckily I still have 4 v8.32 reruns that I expect to finish successfully so I shouldn't be set back to 1 task per day limit next time v8.32 work comes out.

A week wasn't enough !

It reported complete at 12 Nov 2024, 4:47:50 UTC.
The last trickle had been at 01 Nov 2024 15:46:51 UTC.

A week wasn't enough !

It reported complete at 12 Nov 2024, 4:47:50 UTC.
The last trickle had been at 01 Nov 2024 15:46:51 UTC.

The resends due to time outs I have, I found three had completed when I checked. Of the nine I have still running there are just three I have yet to overtake and that should happen by the end of today unless the _0 crunchers get a move on.