at about half the model hadcm3n_4jfo_2020_40_008402337

Maximum CPU time exceeded

Mine got further than the previous deliveries so I would have had a chance to finish it :-/

This might be a series of errors as usually all models of a series have the same FPOPS_BOUND value.

p.s.: I'm not using any tweaks that influence the benchmark result so the calculated FPOPS are standard BOINC, no power saving mode either - that's why it can only be a WU configuration problem.

I've previously only heard about that error when the model is started on one computer, and then transferred to another, much faster, computer.

Still, that unit is now on it's last chance, so it won't bother anyone else.

I did such a move once when I switched that box to Ubuntu for some testing but this time everything has been just standard.

The trickle times where within the normal time/speed range for that box, even somewhat faster than the previous model on the same box.

I can't understand why this model crashed. It's a perfectly normal computer and the trickle times ie processing times are good. If the model got into a loop and stayed stuck there for a long time, that would eventually result in BOINC aborting the model with this error if the model didn't abort itself first. But the trickle times show no evidence of any persistent loop. Other computers have completed models that appear to be from the same batch and took three or four times longer to process.

Could the error possibly be caused by the fact that this computer still has BOINC v.5?

---

Cpdn news