[BUG] Original Markdown CI job fails with an unavailable terminal log #3

Open
opened 2026-09-17 23:45:56 +02:00 by erikinkinen · 0 comments
Owner

Summary

Original lib-bootstrap CI 140 finishes failed in its Markdown job, but the
terminal job log endpoint returns HTTP 500. The Rust test job passes. The missing
log prevents classification of the original failure; a source regression or
runner/service failure has not been established.

Reproduction

Inspect CI 140
at 6c00a68d95e45c0bef7d994901d07754cf33e3f4. The original PR workflow has API
run ID 9634 and failed Markdown job ID 20706, attempt 1. A bounded GET of
/api/v1/repos/erix/lib-bootstrap/actions/jobs/20706/logs?attempt=1 returns
HTTP 500 after the job is terminal. This is one observed original failed job;
clean-checkout reproduction of its unknown cause is not claimed.

Expected and actual behavior

Expected: a terminal job exposes its complete diagnostic log so its failure can
be investigated. Actual: the job status is failure, its log request returns
HTTP 500, and the job response supplies no step details or timestamps explaining
the outcome. The workflow has not been retried, cancelled or replaced.

Environment and identity

  • Component: lib-bootstrap 6c00a68d95e45c0bef7d994901d07754cf33e3f4.
  • Workflow: original pull-request CI 140, Markdown job attempt 1.
  • Build/image: host CI; no guest or image execution is involved.
  • Runner image declared by the workflow: davidanson/markdownlint-cli2.
  • The failing job's actual tool versions and elapsed time are unavailable.
  • Read-only CI status/log access is sufficient; no runtime authority is added.

Evidence and prior checks

The same revision's original push CI 139 passes. The complete successful Rust
job log for CI 140 is retained (29,151 bytes), with no warning candidates. Local
strict Rust and Markdown checks passed on that exact revision. Later original
CI 141 and
CI 142 both pass
at the new coherent dependency revision
d193a3af986b25ca343df7eb647ca4731aac2d0b; that does not explain or erase the
earlier failure. No unavailable log content or root cause is inferred.

Tracking

Related work: #1 and #2. Recover or otherwise establish the original failure
evidence, classify its cause, and address any demonstrated regression. Keep the
original failure visible; do not retry unchanged workflows to obtain a pass.

## Summary Original lib-bootstrap CI 140 finishes failed in its Markdown job, but the terminal job log endpoint returns HTTP 500. The Rust test job passes. The missing log prevents classification of the original failure; a source regression or runner/service failure has not been established. ## Reproduction Inspect [CI 140](https://git.erikinkinen.fi/erix/lib-bootstrap/actions/runs/140) at `6c00a68d95e45c0bef7d994901d07754cf33e3f4`. The original PR workflow has API run ID 9634 and failed Markdown job ID 20706, attempt 1. A bounded GET of `/api/v1/repos/erix/lib-bootstrap/actions/jobs/20706/logs?attempt=1` returns HTTP 500 after the job is terminal. This is one observed original failed job; clean-checkout reproduction of its unknown cause is not claimed. ## Expected and actual behavior Expected: a terminal job exposes its complete diagnostic log so its failure can be investigated. Actual: the job status is failure, its log request returns HTTP 500, and the job response supplies no step details or timestamps explaining the outcome. The workflow has not been retried, cancelled or replaced. ## Environment and identity - Component: lib-bootstrap `6c00a68d95e45c0bef7d994901d07754cf33e3f4`. - Workflow: original pull-request CI 140, Markdown job attempt 1. - Build/image: host CI; no guest or image execution is involved. - Runner image declared by the workflow: `davidanson/markdownlint-cli2`. - The failing job's actual tool versions and elapsed time are unavailable. - Read-only CI status/log access is sufficient; no runtime authority is added. ## Evidence and prior checks The same revision's original push CI 139 passes. The complete successful Rust job log for CI 140 is retained (29,151 bytes), with no warning candidates. Local strict Rust and Markdown checks passed on that exact revision. Later original [CI 141](https://git.erikinkinen.fi/erix/lib-bootstrap/actions/runs/141) and [CI 142](https://git.erikinkinen.fi/erix/lib-bootstrap/actions/runs/142) both pass at the new coherent dependency revision `d193a3af986b25ca343df7eb647ca4731aac2d0b`; that does not explain or erase the earlier failure. No unavailable log content or root cause is inferred. ## Tracking Related work: #1 and #2. Recover or otherwise establish the original failure evidence, classify its cause, and address any demonstrated regression. Keep the original failure visible; do not retry unchanged workflows to obtain a pass.
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/lib-bootstrap#3
No description provided.