[BUG] Docs CI jobs fail while their original logs return HTTP 500 #11

Open
opened 2026-09-23 19:54:28 +02:00 by erikinkinen · 0 comments
Owner

Summary

Docs PR CI run 1042 reports a failed Markdown job, but the corresponding Forgejo log request returns HTTP 500. The original failure cannot yet be attributed to linting, container setup, checkout, runner execution or log storage. This leaves a regression result unexplained even though the paired push and newer independently changed revisions pass.

Reproduction

  1. Inspect the original pull-request workflow 1042, attempt 1, for commit d806080008b7bad02eb1df0ddd4f1c3fdd4dd024.
  2. The run/jobs response reports manual: success and markdown: failure.
  3. A bounded read of /api/v1/repos/erix/docs/actions/jobs/22334/logs?attempt=1 returns HTTP 500 without a job log. The same log retrieval problem was observed while this original job still reported running.

One failing workflow is established. The job has not been rerun; no clean-checkout reproduction of the failure or causal fix is established. The workflow requests a Docker runner and the davidanson/markdownlint-cli2 image, installs Git with apk, checks out the exact selected revision, then runs markdownlint-cli2. The absent log does not establish which step ran or failed.

Expected and actual behavior

Expected: the selected Markdown workflow completes with an inspectable terminal log, or supplies enough retained failure evidence to identify the failed step and exit status.

Actual: the run reports failure and its Markdown job reports failure, while the log endpoint returns HTTP 500. The run spans 16:30:52–17:34:52 UTC on 23 September 2026. This 64-minute run duration alone does not prove a timeout cause. The command exit status and failed step remain unavailable. The manual job succeeds and its complete retained log has a clean final TeX pass.

Environment and identity

  • Component repository/revision: Docs d806080008b7bad02eb1df0ddd4f1c3fdd4dd024, PR workflow for review #4.
  • Image/profile: documentation CI; no EriX boot image or guest execution. The requested Markdown container is davidanson/markdownlint-cli2; its resolved digest and executed tool version cannot be verified without the job log.
  • Hardware/runtime: Docker-labelled runner; actual runner/container state at failure is not established.
  • Route/authority: ordinary repository CI plus read-only status/log observation. No workflow restart, runner/configuration mutation or release action was used to investigate this result.
  • Comparison: paired push run 1041 passes on the same selected commit. Later runs 1043 and 1044 pass on separately changed commit 64a208cb69c6bc7fa707c8bab825cfcbdd38e9a7. These are distinct observations, not a reproduction or repair of run 1042.

Evidence and prior checks

Additional original failures — 28 September 2026: PR run 1103 and push run 1104, attempt 1, both fail on Docs a42c89f1. Run 1103 has successful manual job 23303 and failed Markdown job 23304. Run 1104 has failed manual job 23305 and failed Markdown job 23306. Bounded GET requests to each of the three failed jobs' /actions/jobs/<id>/logs?attempt=1 endpoints return HTTP 500, leaving failed steps and command exit statuses unavailable. The complete 408,588-byte log for job 23303 verifies the exact checkout, 45 passing controls, a 2,657-page manual and no warnings in the final TeX pass. Earlier-pass reference warnings are retained. The successful manual and local checks do not explain the other failures. No unchanged job was rerun; no common cause or repair is established.

Original run/job responses and bounded log-error observations are retained. The successful manual log for run 1042 is complete: 384,013 bytes, SHA-256 ae32ae497260f44321b8fe8b10e0b064705849789b97daf535e47a943ec23416. It passes 45 document tests and builds 2,437 pages; preliminary reference warnings precede the clean final pass. Local Markdown/manual checks and paired successful CI do not explain the failed job or missing log. No unchanged failing input has been rerun for acceptance.

Tracking

Related: documentation build quality #1, audit #2, review #4, and Phase 6 completion.

  • Recover the original failed manual and Markdown execution/failure evidence, or document the precise evidence-loss boundary.
  • Establish whether runner, container/setup, checkout, lint execution or log storage caused the reported failure.
  • Correct the established cause while preserving lint coverage and original failure evidence.
  • Validate the correction with changed, identified inputs; retain uncertainty if the original failure remains unattributed.
## Summary Docs PR CI run [1042](https://git.erikinkinen.fi/erix/docs/actions/runs/1042) reports a failed Markdown job, but the corresponding Forgejo log request returns HTTP 500. The original failure cannot yet be attributed to linting, container setup, checkout, runner execution or log storage. This leaves a regression result unexplained even though the paired push and newer independently changed revisions pass. ## Reproduction 1. Inspect the original pull-request workflow [1042](https://git.erikinkinen.fi/erix/docs/actions/runs/1042), attempt 1, for commit `d806080008b7bad02eb1df0ddd4f1c3fdd4dd024`. 2. The run/jobs response reports `manual: success` and `markdown: failure`. 3. A bounded read of `/api/v1/repos/erix/docs/actions/jobs/22334/logs?attempt=1` returns HTTP 500 without a job log. The same log retrieval problem was observed while this original job still reported running. One failing workflow is established. The job has not been rerun; no clean-checkout reproduction of the failure or causal fix is established. The workflow requests a Docker runner and the `davidanson/markdownlint-cli2` image, installs Git with `apk`, checks out the exact selected revision, then runs `markdownlint-cli2`. The absent log does not establish which step ran or failed. ## Expected and actual behavior Expected: the selected Markdown workflow completes with an inspectable terminal log, or supplies enough retained failure evidence to identify the failed step and exit status. Actual: the run reports failure and its Markdown job reports failure, while the log endpoint returns HTTP 500. The run spans 16:30:52–17:34:52 UTC on 23 September 2026. This 64-minute run duration alone does not prove a timeout cause. The command exit status and failed step remain unavailable. The manual job succeeds and its complete retained log has a clean final TeX pass. ## Environment and identity - Component repository/revision: [Docs `d806080008b7bad02eb1df0ddd4f1c3fdd4dd024`](https://git.erikinkinen.fi/erix/docs/commit/d806080008b7bad02eb1df0ddd4f1c3fdd4dd024), PR workflow for [review #4](https://git.erikinkinen.fi/erix/docs/pulls/4). - Image/profile: documentation CI; no EriX boot image or guest execution. The requested Markdown container is `davidanson/markdownlint-cli2`; its resolved digest and executed tool version cannot be verified without the job log. - Hardware/runtime: Docker-labelled runner; actual runner/container state at failure is not established. - Route/authority: ordinary repository CI plus read-only status/log observation. No workflow restart, runner/configuration mutation or release action was used to investigate this result. - Comparison: paired push run [1041](https://git.erikinkinen.fi/erix/docs/actions/runs/1041) passes on the same selected commit. Later runs [1043](https://git.erikinkinen.fi/erix/docs/actions/runs/1043) and [1044](https://git.erikinkinen.fi/erix/docs/actions/runs/1044) pass on separately changed commit `64a208cb69c6bc7fa707c8bab825cfcbdd38e9a7`. These are distinct observations, not a reproduction or repair of run 1042. ## Evidence and prior checks Additional original failures — 28 September 2026: [PR run 1103](https://git.erikinkinen.fi/erix/docs/actions/runs/1103) and [push run 1104](https://git.erikinkinen.fi/erix/docs/actions/runs/1104), attempt 1, both fail on [Docs a42c89f1](https://git.erikinkinen.fi/erix/docs/commit/a42c89f10451dbb79292fb6f7f06f57a2fc6c195). Run 1103 has successful manual job 23303 and failed Markdown job 23304. Run 1104 has failed manual job 23305 and failed Markdown job 23306. Bounded GET requests to each of the three failed jobs' `/actions/jobs/<id>/logs?attempt=1` endpoints return HTTP 500, leaving failed steps and command exit statuses unavailable. The complete 408,588-byte log for job 23303 verifies the exact checkout, 45 passing controls, a 2,657-page manual and no warnings in the final TeX pass. Earlier-pass reference warnings are retained. The successful manual and local checks do not explain the other failures. No unchanged job was rerun; no common cause or repair is established. Original run/job responses and bounded log-error observations are retained. The successful manual log for run 1042 is complete: 384,013 bytes, SHA-256 `ae32ae497260f44321b8fe8b10e0b064705849789b97daf535e47a943ec23416`. It passes 45 document tests and builds 2,437 pages; preliminary reference warnings precede the clean final pass. Local Markdown/manual checks and paired successful CI do not explain the failed job or missing log. No unchanged failing input has been rerun for acceptance. ## Tracking Related: [documentation build quality #1](https://git.erikinkinen.fi/erix/docs/issues/1), [audit #2](https://git.erikinkinen.fi/erix/docs/issues/2), [review #4](https://git.erikinkinen.fi/erix/docs/pulls/4), and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [ ] Recover the original failed manual and Markdown execution/failure evidence, or document the precise evidence-loss boundary. - [ ] Establish whether runner, container/setup, checkout, lint execution or log storage caused the reported failure. - [ ] Correct the established cause while preserving lint coverage and original failure evidence. - [ ] Validate the correction with changed, identified inputs; retain uncertainty if the original failure remains unattributed.
erikinkinen changed title from [BUG] Markdown CI fails while its original job log returns HTTP 500 to [BUG] Docs CI jobs fail while their original logs return HTTP 500 2026-09-28 22:32:29 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:40 +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/docs#11
No description provided.