[BUG] Original CI fails without retrievable Rust or Markdown logs #8
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/launchd#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Original Launchd CI164 now reports failure for both Rust and Markdown, but both original attempt-1 job-log endpoints return HTTP 500. The missing logs prevent determining whether the underlying failure was in the source, runner or CI service. No product regression or common cause with another report is established.
Reproduction
Inspect original CI164 at commit
9fc3c73b917e249c61c3ebdc30f883c5f940ac2c, then request its Rust job 22923 and Markdown job 22924 logs through the deployed Forgejo API:The requests used bounded byte ranges and the existing authenticated read-only route. The same endpoints returned HTTP 500 while the run was still reported running and after it became terminal. No workflow rerun or source change was used to produce these observations.
Expected and actual behavior
Expected: the original terminal jobs expose their complete diagnostic logs so the failure can be classified and corrected.
Actual: both jobs report failure, both log GETs return HTTP 500, and no log bytes are retrieved. The run started at 03:04:57 UTC and stopped at 04:09:52 UTC on 25 September 2026. These status times alone do not establish a timeout or runner failure as the cause.
Environment and identity
feature/posix-compat.9fc3c73b917e249c61c3ebdc30f883c5f940ac2c.dockerlabel. The actual failing command and worker condition cannot be recovered from the available logs.Evidence and prior checks
The exact original run/job status responses and bounded HTTP failure observations are retained. CI163's complete Rust/Markdown logs verify 78,965 bytes with zero warnings; the signed source also passes 430 tests in each of six maintained local configurations, strict host/native Clippy, rustdoc and warning-denied native builds. Those successful checks do not explain or override CI164's failure. The later append/freeze source also passes its original push CI165; that is a different revision and is not substituted for this run.
Tracking
Track diagnosis alongside Launchd PR2 and Phase 6 completion. Posixd's unavailable Markdown-log report records a similar observability problem; a shared cause is unproved. Preserve the original attempts, recover their diagnostics where possible, and correct any identified source or CI defect without relaxing validation gates.
erikinkinen referenced this issue2026-09-25 06:30:56 +02:00