[BUG] Component CI failures have no retrievable worker logs #153

Closed
opened 2026-10-17 04:37:31 +02:00 by erikinkinen · 2 comments
Owner

Summary

Failed jobs in 21 component runs have no retrievable worker logs. Forgejo's run-log archives contain 29 .MISSING entries instead of their failed-job output. This prevents diagnosis of the original failures.

Reproduction

Open a failed job in LibBlock CI232 or LibPosixABI CI254, or download the run's logs. The archive reports that the corresponding actions_log file does not exist.

Expected and actual behavior

Failed runs should retain enough output to identify the failing step. The failed-job bodies are missing, while thirteen successful-job logs in the same set of archives remain available. Missing logs establish neither a compiler failure nor a common cause for the runs.

Environment and identity

The affected repositories are LibAes, LibBlock, LibBootimg, LibCapabi, LibDynlink, LibEd25519, LibElf, LibFsCrypto, LibFsName, LibHandoff, LibPartition, LibPosixABI, LibSha2, LibStdio, LibTime, LibVfs, Deviced, Fbcond, Probed, Ttyd and Vfsd. All are push runs on feature/posix-compat; their original source, job, task and attempt identities are preserved.

Evidence and prior checks

All 21 original archives were downloaded successfully and inspected in full. Every failed-job entry reports a missing file. The original runs remain failed.

LibCstd #7 previously had missing logs and later passed in a separate manual run at unchanged source. That did not restore its original logs. Fresh runs for these components must likewise remain separate from the originals. LibPosixABI requires the separate source repair in #9.

Tracking

  • Preserve the original failed runs and complete missing-log responses.
  • Start one separate run at unchanged source for each of the 20 eligible components, recording any refusal or uncertain result before another action.
  • Inspect the fresh terminal results and logs; record passes or report concrete failures separately.

Fresh verification does not establish that the worker log store has been repaired.

## Summary Failed jobs in 21 component runs have no retrievable worker logs. Forgejo's run-log archives contain 29 `.MISSING` entries instead of their failed-job output. This prevents diagnosis of the original failures. ## Reproduction Open a failed job in [LibBlock CI232](https://git.erikinkinen.fi/erix/lib-block/actions/runs/232) or [LibPosixABI CI254](https://git.erikinkinen.fi/erix/lib-posixabi/actions/runs/254), or download the run's logs. The archive reports that the corresponding `actions_log` file does not exist. ## Expected and actual behavior Failed runs should retain enough output to identify the failing step. The failed-job bodies are missing, while thirteen successful-job logs in the same set of archives remain available. Missing logs establish neither a compiler failure nor a common cause for the runs. ## Environment and identity The affected repositories are LibAes, LibBlock, LibBootimg, LibCapabi, LibDynlink, LibEd25519, LibElf, LibFsCrypto, LibFsName, LibHandoff, LibPartition, LibPosixABI, LibSha2, LibStdio, LibTime, LibVfs, Deviced, Fbcond, Probed, Ttyd and Vfsd. All are push runs on `feature/posix-compat`; their original source, job, task and attempt identities are preserved. ## Evidence and prior checks All 21 original archives were downloaded successfully and inspected in full. Every failed-job entry reports a missing file. The original runs remain failed. [LibCstd #7](https://git.erikinkinen.fi/erix/lib-cstd/issues/7) previously had missing logs and later passed in a separate manual run at unchanged source. That did not restore its original logs. Fresh runs for these components must likewise remain separate from the originals. LibPosixABI requires the separate source repair in [#9](https://git.erikinkinen.fi/erix/lib-posixabi/issues/9). ## Tracking - [x] Preserve the original failed runs and complete missing-log responses. - [x] Start one separate run at unchanged source for each of the 20 eligible components, recording any refusal or uncertain result before another action. - [x] Inspect the fresh terminal results and logs; record passes or report concrete failures separately. Fresh verification does not establish that the worker log store has been repaired.
Author
Owner

All 15 separate runs have started at unchanged source, with one dispatch each. The original failed jobs and their missing-log responses remain preserved. Fresh results and execution logs are the remaining step; LibPosixABI is still held for its C-probe fix.

All 15 separate runs have started at unchanged source, with one dispatch each. The original failed jobs and their missing-log responses remain preserved. Fresh results and execution logs are the remaining step; LibPosixABI is still held for [its C-probe fix](https://git.erikinkinen.fi/erix/lib-posixabi/issues/9).
Author
Owner

The 20 separate recovery runs are now accounted for: 19 pass with complete, warning-free logs; Vfsd reaches a reproducible helper import error tracked in Vfsd #35. Its repair is published in 0830021c. LibPosixABI’s separate source repair is tracked in #9.

This completes the recovery work. The original 21 failed runs and their missing logs remain unchanged; this does not establish a repair to the worker log store.

The 20 separate recovery runs are now accounted for: 19 pass with complete, warning-free logs; Vfsd reaches a reproducible helper import error tracked in [Vfsd #35](https://git.erikinkinen.fi/erix/vfsd/issues/35). Its repair is published in 0830021c. LibPosixABI’s separate source repair is tracked in [#9](https://git.erikinkinen.fi/erix/lib-posixabi/issues/9). This completes the recovery work. The original 21 failed runs and their missing logs remain unchanged; this does not establish a repair to the worker log store.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:19 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#153
No description provided.