[BUG] Failed original CI jobs return HTTP 500 for logs #3

New issue

Closed

opened 2026-09-19 11:03:54 +02:00 by erikinkinen · 0 comments

erikinkinen commented

2026-09-19 11:03:54 +02:00

Owner

Summary

Resolved by user-triggered reruns, verified 19 September 2026: CI 97 (attempt 1), CI 98 (attempt 2), pass at unchanged commit 6783df35e4fae8c01ff3d281f0ec9d047892e986. All four test/Markdown job logs are complete and hashed (110,409 bytes), with zero warning or failure candidates. This resolves the current validation blockage. Original failed-attempt status and HTTP 500 observations remain history; their missing output and causes are not recovered or explained by this result. No source fix is claimed.

Initial observation before the reruns: Original failed CI jobs have unavailable logs, preventing diagnosis and complete acceptance. No code-level cause is established.

Reproduction

Inspect CI 98, then request the original job logs through an authorized Forgejo API client. Observed on 19 September 2026:

GET /api/v1/repos/erix/loaderd/actions/jobs/21264/logs?attempt=1 returns HTTP 500.

Expected and actual behavior

Expected: terminal jobs expose their complete original output. Actual: the selected log endpoints return HTTP 500. Missing output cannot establish the failure cause or warning count.

Environment and identity

Repository loaderd, signed commit 6783df35e4fae8c01ff3d281f0ec9d047892e986, branch feature/posix-compat, original push/PR workflows. Missing job environment details and an introducing revision are unestablished. No VM outcome is inferred.

Evidence and prior checks

Verified rerun evidence:

Workflow	Job	Attempt	Complete log bytes	SHA-256
97	21261	1	51594	`76a0cf4110948d1fff3df73ecb2459e0121bced9a8ea58989de32300bd04c2df`
97	21262	1	3603	`c9d9af4a2c7e53600c21270a64d60a07070197ea786cfd9b6477da0fedf8b33b`
98	21263	2	51601	`1107ae2ed535de2fb9e6013f82973782a7f10a9fa3929511cb9f3ff1547cb415`
98	21264	2	3611	`4d79b9badde4398fc41bc765e70ac7ade373cde573f309d6f77a0be8c98e5f1c`

Original observations, retained as history:

Loaderd CI 98 test succeeds with a complete 51,603-byte log; paired CI 97 also succeeds from complete logs. Available complete logs contain no warnings. Local strict Rust/native/documentation checks also pass, but cannot replace missing CI evidence. Original snapshots and failed HTTP responses are retained. At that original observation no workflow had been rerun or cancelled.

Tracking

Feature issue 1, PR 2. Closed as resolved by the user-triggered reruns on the evidence above. No code change or infrastructure root cause is established. Preserve both attempts and reopen if the failure recurs; retain all required source, authority, warning and VM gates.

## Summary Resolved by user-triggered reruns, verified 19 September 2026: [CI 97](https://git.erikinkinen.fi/erix/loaderd/actions/runs/97) (attempt 1), [CI 98](https://git.erikinkinen.fi/erix/loaderd/actions/runs/98) (attempt 2), pass at unchanged commit `6783df35e4fae8c01ff3d281f0ec9d047892e986`. All four test/Markdown job logs are complete and hashed (110,409 bytes), with zero warning or failure candidates. This resolves the current validation blockage. Original failed-attempt status and HTTP 500 observations remain history; their missing output and causes are not recovered or explained by this result. No source fix is claimed. Initial observation before the reruns: Original failed CI jobs have unavailable logs, preventing diagnosis and complete acceptance. No code-level cause is established. ## Reproduction Inspect [CI 98](https://git.erikinkinen.fi/erix/loaderd/actions/runs/98), then request the original job logs through an authorized Forgejo API client. Observed on 19 September 2026: - `GET /api/v1/repos/erix/loaderd/actions/jobs/21264/logs?attempt=1` returns HTTP 500. ## Expected and actual behavior Expected: terminal jobs expose their complete original output. Actual: the selected log endpoints return HTTP 500. Missing output cannot establish the failure cause or warning count. ## Environment and identity Repository `loaderd`, signed commit `6783df35e4fae8c01ff3d281f0ec9d047892e986`, branch `feature/posix-compat`, original push/PR workflows. Missing job environment details and an introducing revision are unestablished. No VM outcome is inferred. ## Evidence and prior checks Verified rerun evidence: | Workflow | Job | Attempt | Complete log bytes | SHA-256 | | --- | --- | --- | --- | --- | | 97 | 21261 | 1 | 51594 | `76a0cf4110948d1fff3df73ecb2459e0121bced9a8ea58989de32300bd04c2df` | | 97 | 21262 | 1 | 3603 | `c9d9af4a2c7e53600c21270a64d60a07070197ea786cfd9b6477da0fedf8b33b` | | 98 | 21263 | 2 | 51601 | `1107ae2ed535de2fb9e6013f82973782a7f10a9fa3929511cb9f3ff1547cb415` | | 98 | 21264 | 2 | 3611 | `4d79b9badde4398fc41bc765e70ac7ade373cde573f309d6f77a0be8c98e5f1c` | Original observations, retained as history: Loaderd CI 98 test succeeds with a complete 51,603-byte log; paired CI 97 also succeeds from complete logs. Available complete logs contain no warnings. Local strict Rust/native/documentation checks also pass, but cannot replace missing CI evidence. Original snapshots and failed HTTP responses are retained. At that original observation no workflow had been rerun or cancelled. ## Tracking [Feature issue 1](https://git.erikinkinen.fi/erix/loaderd/issues/1), [PR 2](https://git.erikinkinen.fi/erix/loaderd/pulls/2). Closed as resolved by the user-triggered reruns on the evidence above. No code change or infrastructure root cause is established. Preserve both attempts and reopen if the failure recurs; retain all required source, authority, warning and VM gates.

erikinkinen added the

bug

phase-6

labels

2026-09-19 11:03:54 +02:00

erikinkinen referenced this issue

2026-09-19 11:08:14 +02:00

[FEATURE] Audit authority, code quality and documentation in loaderd #1

erikinkinen referenced this issue

2026-09-19 11:08:14 +02:00

WIP: Enforce native RELRO and stage exact realm mediators #2

erikinkinen closed this issue