R-887: three CI jobs lost today, all ending at :45:58 past the hour
gates / gates (push) Successful in 6m0s

1631 (catalog b7f0f7c), 1632 (felhom.eu 970616b7) and 1634 (felhom.eu 29c9cb1e):
every step failure with 0 s after 10.5-14 minutes in set-up, logs absent. A job
never picked up would end at an arbitrary second; the same second-of-the-hour
twice two hours apart points at a periodic sweep or a fixed deadline. Between
them the runner worked — catalog job 1633 succeeded normally on the same tree,
and a shallow clone with no sibling runs the catalog gates green by hand, so the
code is not what is red. The 2026-10-12 due-check's premise is false and the row
now says so.
This commit is contained in:
2026-10-10 14:46:47 +02:00
parent 29c9cb1e9a
commit cf1e137129
2 changed files with 21 additions and 1 deletions
+20
View File
@@ -148,3 +148,23 @@ aborted the whole runner at the first gate.
ran no gate by itself. `catalog_gates.py grocy lubelogger --fast` was run by hand immediately
before the commit and was green, and the two runtime gates were run on the bench; CI re-ran the
entry point on the push. No `--no-verify` was used anywhere.
## 10. CI, read by pulling (the standing rule), by job id
| repo | commit | job | conclusion |
|---|---|---|---|
| app-catalog-felhom.eu | `b7f0f7c` (the publish) | 1631 | **failure — R-887's lost job, not the code** |
| app-catalog-felhom.eu | `8ea72aa` (the same tree + one line) | 1633 | **success** |
| felhom.eu | `970616b7` | 1632 | **failure — the same lost job** |
| felhom.eu | `29c9cb1e` | 1634 | **failure — the same lost job, a third time** |
**All THREE lost jobs ended at :45:58 past the hour** (1631 and 1632 at 10:45:58Z, 1634 at 12:45:58Z) — catalog job 1631 after ~14 minutes
in set-up with three steps, felhom.eu job 1632 after ~11.5 minutes with seven, every step `failure`
with 0 s, and both logs answering `file does not exist`. A per-job fault cannot do that; one runner
event took both, and the runner pod had been restarted earlier the same day. That is new information
for **R-887**, whose row and whose 2026-10-12 due-check now say so: the check's premise ("no CI job
lost since 2026-10-05 16:00Z") is false.
**What proves the code rather than the runner:** the same catalogue tree passed as job 1633, and a
shallow clone with no sibling repository — the CI shape — runs all nine applicable gates green by hand
(`/tmp/cisim` on DooPlex, reproduced deliberately rather than assumed).
File diff suppressed because one or more lines are too long