You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not entirely sure of what's going on, but my hunch is that Malt had troubles syncing up with the workers on this machine? I retried multiple times, after your retry, still haven't caught the same error again.
After 15 retries (for 15 jobs, total of 225 new jobs) still no sign of the same error again. Oceananigans CI has been running non-stop today with v2.9.0 and we haven't seen anything dodgy so far, and I'm having a hard time seeing how 0be4b81 could be problematic (it's modifying a Set, but under a lock).
Running 8 tests using 4 parallel jobs. To change the number of jobs, specify the `--jobs=N` argument to the tests, or set the `PTR_NUM_JOBS` environment variable.
Available memory: 11.339 GiB; Max worker RSS: 3.711 GiB
│ Test │ Init │ Compile │ ──────────────── CPU ──────────────── │
Test (Worker) │ time (s) │ time (s) │ (%) │ GC (s) │ GC % │ Alloc (MB) │ RSS (MB) │
history (3) │ started at 2026-09-21T01:35:49.138
retries (2) │ started at 2026-09-21T01:35:49.539
serial (4) │ started at 2026-09-21T01:35:49.678
workers (1) │ started at 2026-09-21T01:35:49.779
retries (2) │ 181.78 │ 14.52 │ failed at 2026-09-21T01:38:54.124
output (2) │ started at 2026-09-21T01:38:54.167
history (3) │ 198.99 │ 14.32 │ failed at 2026-09-21T01:39:10.600
core (3) │ started at 2026-09-21T01:39:10.600
serial (4) │ 204.10 │ 14.47 │ failed at 2026-09-21T01:39:15.865
failures (4) │ started at 2026-09-21T01:39:15.881
output (2) │ 55.42 │ 0.47 │ 5.28 │ 0.04 │ 0.1 │ 185.71 │ 426.35 │
unit (2) │ started at 2026-09-21T01:39:49.900
workers (1) │ 238.06 │ 15.01 │ failed at 2026-09-21T01:39:50.043
unit (2) │ 1.22 │ 0.44 │ 69.33 │ 0.00 │ 0.0 │ 42.08 │ 426.35 │
failures (4) │ 42.89 │ 0.45 │ 2.85 │ 0.00 │ 0.0 │ 45.31 │ 510.09 │
core (3) │ 50.87 │ 0.40 │ 9.22 │ 0.04 │ 0.1 │ 211.15 │ 450.02 │
The init time of the fresh workers was exceptionally long, I checked other Windows jobs and it's usually around 7-8 seconds (which is still long-ish compared to the other OSes, but that's what it is), so this points in the direction of "we just got an unlucky machine" (I swear I only gave the bot the raw log, didn't link to this issue!).
Activity
giordano commentedon Sep 21, 2026
Since the log files are ephemeral, the errors are all like this
I'm not entirely sure of what's going on, but my hunch is that Malt had troubles syncing up with the workers on this machine? I retried multiple times, after your retry, still haven't caught the same error again.
christiangnrd commentedon Sep 21, 2026
Do we just tag 2.9.1 and hope it was a fluke?
giordano commentedon Sep 21, 2026
After 15 retries (for 15 jobs, total of 225 new jobs) still no sign of the same error again. Oceananigans CI has been running non-stop today with v2.9.0 and we haven't seen anything dodgy so far, and I'm having a hard time seeing how 0be4b81 could be problematic (it's modifying a
Set, but under a lock).One thing that the bot pointed out to me in the log of the failed job is https://github.com/JuliaTesting/ParallelTestRunner.jl/actions/runs/35551060457/job/106185841081#step:5:146
The init time of the fresh workers was exceptionally long, I checked other Windows jobs and it's usually around 7-8 seconds (which is still long-ish compared to the other OSes, but that's what it is), so this points in the direction of "we just got an unlucky machine" (I swear I only gave the bot the raw log, didn't link to this issue!).
christiangnrd commentedon Sep 21, 2026
Alright I say we leave this open for a bit just in case and I’ve triggered the registrator