Results-saving job stopped early after running out of its 6-hour limit
Dynamic compositional representations ยท October 17, 2026
On 2026-10-17, a job saving results on a transfer node stopped early when it ran out of its allowed 6 hours. The study stands at 4,377 of 6,068 runs finished (72.1%), with no runs running and none waiting.
What ran
One job saving results ran on a transfer node with 2 CPU cores. It was submitted and started at 2026-10-16 23:06 UTC and ended at 2026-10-17 05:06 UTC.
What finished
No runs finished on 2026-10-17; the run counts are unchanged from the previous day. The job that ran was charged 0.05 node-hours.
The numbers
- Runs finished: 4,377 of 6,068 (72.1%)
- Runs running: 0
- Runs waiting: 0
- Runs failed: 3
- Runs interrupted: 20
- Runs not started: 1,668
- Node-hours used so far: 150.18
- Mean run time: 6.8 minutes
- Result cells with results: 584 of 821, of which 578 are complete
- The job ran for 6 h against a 6 h time limit
Failures and what was done
The job saving results stopped early because it ran out of its allowed time. Its exit code was 0:0. In the ffn1-lm grid, three runs failed with exit code 1 in job 3583877: ffn1-lm__W4__s0, ffn1-lm__W4__s1, and ffn1-lm__W4__s2. Several runs in cut5, cut8b, interject1, cut4c, and weight-w4a hold locks from jobs that have ended.
What was learned
Nothing new was learned; there are no notebook entries or reviews in the facts.
What was decided
Nothing new was decided; there are no notebook entries, reviews, or commits in the facts.
What is next
The queue is empty: no jobs are running or waiting. Several grids have nothing queued and are not finished: grid2-role (0 of 177), fold1 (0 of 36), fold1b (0 of 14), fold1c-lm (0 of 12), ctx3-lm (0 of 6), cut5 (157 of 288), cut8b (210 of 252), and weight-w4a (116 of 324). No next step is named in a notebook entry.