[BUG] Failed original CI jobs return HTTP 500 for logs #3
Labels
No labels
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/probed#3
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
Resolved by user-triggered reruns, verified 19 September 2026: CI 71 (attempt 2), CI 72 (attempt 2), pass at unchanged commit
6405b1425f8a707d0638177e5f2fc0192f1a7d03. All four test/Markdown job logs are complete and hashed (80,198 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 72, CI 71, then request the original job logs through an authorized Forgejo API client. Observed on 19 September 2026:
GET /api/v1/repos/erix/probed/actions/jobs/21251/logs?attempt=1returns HTTP 500.GET /api/v1/repos/erix/probed/actions/jobs/21252/logs?attempt=1returns HTTP 500.GET /api/v1/repos/erix/probed/actions/jobs/21250/logs?attempt=1returns 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
probed, signed commit6405b1425f8a707d0638177e5f2fc0192f1a7d03, branchfeature/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:
1defb0045ab4019d7d4fed8511e3c470b11217b873639d679b732a6a65efe4a5df3e04473a637335746e5ca2385230937edaf0823b086b261a7546b43aee44718b84e958b3bf0b3a721acf9bed05bf6e248c1c0b314a5cb8381b96a3a45b4041f15b61f9d7e761c74a212127497dc2c002760903e44d7d4efd9145c83ff79623Original observations, retained as history:
Probed CI 71 test succeeds with a complete 36,491-byte log. 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.
erikinkinen referenced this issue from erix/integration2026-09-19 11:36:52 +02:00