Commit bc8d6ac
committed
fix(ci): bump apt-get timeout 300→600 in nightly workflows (#125)
The 2026-06-18 nightly diff-fuzz run failed at the C++ build deps step
with exit code 124. The job had been running ~5 minutes (16:49 → 16:54
UTC), which matches `timeout 300` exactly:
```
16:49:29 Run timeout 300 sudo apt-get update + timeout 300 sudo apt-get install ...
16:54:09 Get:4 cmake-data (2155 kB)
16:54:26 Get:5 cmake amd64 (11.2 MB)
16:54:36 exit code 124
```
The previous 10 nightly runs took 4:30~4:50 hours total, so the global
job budget (`timeout-minutes: 355` + `timeout 340m` on the fuzz step)
was nowhere near being hit. The failure is purely the apt step's
per-command guard tripping during a slow Azure mirror cycle.
Bump `timeout 300` → `600` on both `apt-get update` and
`apt-get install` in nightly-diff-fuzz.yml and nightly-benchmark.yml
(both have the identical idiom). 600s = 10 minutes is still a hard
ceiling, just lenient enough to absorb the kind of mirror congestion
the 06-18 run hit (cmake 11.2 MB alone took ~17s post-cmake-data, both
combined ran over 5 minutes).
Closes #125.
Does not address #109 / #124 — those are a separate go-vs-cpp
column/row-store divergence pattern that needs root-cause investigation
beyond infra fixes.1 parent 6471007 commit bc8d6ac
2 files changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
48 | | - | |
| 47 | + | |
| 48 | + | |
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
52 | | - | |
53 | | - | |
| 52 | + | |
| 53 | + | |
54 | 54 | | |
55 | 55 | | |
56 | 56 | | |
| |||
0 commit comments