I noticed a job waiting to report had failed with a computation error. Checking, I found that since 27th of January, I'd had 42 of these, all, bar one, having less than 5 seconds of CPU time, (one had 5.08 seconds). Are others seeing this also?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I noticed a job waiting to report had failed with a computation error. Checking, I found that since 27th of January, I'd had 42 of these, all, bar one, having less than 5 seconds of CPU time, (one had 5.08 seconds). Are others seeing this also?

Yes. In my case between 20 & 25% error out :(
Given they only run a few seconds or minutes before crashing out, it's more the project's problem than ours. Just highly annoying.
It's one of those issues where it's easier to let them run and fail than try to extract the bad tasks, where some good ones may be mistakenly taken out in the process, so close your eyes and let the batch work its own way through.
This has been the project's active policy when the issue has arisen previously, so reporting it is a little futile. They'll have seen it's happening almost from the outset.

---

Yes, but asking what I asked indicates the "problem" is not with my rig.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Yes, but asking what I asked indicates the "problem" is not with my rig.

Sorry, yes, quite right

---