21 Sep
2026
21 Sep
'26
5:42 p.m.
On 9/21/26 12:07 pm, James Jardine via slurm-users wrote:
Jobs that ended in TIMEOUT were about 6.6% of jobs but roughly 45% of total job energy. That follows once you say it out loud: a timed-out job runs its full wall-clock request by definition, and then returns nothing.
That's not necessarily true, it ran to the timelimit true, but that might be the users intention, they could be doing regular checkpoints and then restarting from them to carry on their simulation/calculation. We see that a lot. So I would caution against drawing that sort of conclusion without checking with the users running those jobs. All the best, Chris