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

New issue

Closed

opened 2026-09-18 09:07:44 +02:00 by erikinkinen · 0 comments

erikinkinen commented

2026-09-18 09:07:44 +02:00

Owner

Summary

Resolved by user-triggered reruns, verified 19 September 2026: CI 74 (attempt 2), CI 75 (attempt 1), pass at unchanged commit ed6473c6e741b1c3b8049f2dffb2a959c475c5ac. All four test/Markdown job logs are complete and hashed (62,791 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 inputd CI reports failed jobs whose log endpoints return HTTP 500. The missing logs prevent diagnosis and complete CI acceptance for the selected source. The cause of either the job failures or log-service errors is not established.

Reproduction

Inspect CI 74 at the original selected commit, then request the original job logs with an authorized Forgejo API client:

GET /api/v1/repos/erix/inputd/actions/jobs/21213/logs?attempt=1 → HTTP 500.
GET /api/v1/repos/erix/inputd/actions/jobs/21214/logs?attempt=1 → HTTP 500.

Each listed request returned HTTP 500 in the retained terminal-status observation on 18 September 2026. At that original observation the workflows had not been rerun or cancelled.

Expected and actual behavior

Expected: every terminal job exposes its complete original log, including the failure and cleanup outcome. Actual: Forgejo reports failure for the selected jobs but returns HTTP 500 for their logs. No complete log, warning count or code-level failure cause can be inferred for those jobs.

Environment and identity

Repository: inputd at ed6473c6e741b1c3b8049f2dffb2a959c475c5ac on feature/posix-compat.
Execution: original Forgejo push/PR workflows and the job-attempt selectors above.
Image/VM: these are component validation jobs; no guest outcome is inferred.
Toolchain/runtime details for the missing jobs: unavailable until their original logs are recovered.
Last known working revision for log retrieval: not established.

Evidence and prior checks

Verified rerun evidence:

Workflow	Job	Attempt	Complete log bytes	SHA-256
74	21213	2	27786	`cd7fff7e9a0abb84b3b8cbe238a1b03b45229b7ecc6f253cd0b192b350616da1`
74	21214	2	3601	`855081b4a2895958ac89051028b9ccf429b4e4e74be38299c584ccb709b18572`
75	21215	1	27795	`4b313fdc87bb55812fc77671bd08c11d19371bb983cc692320792ffc18961bc0`
75	21216	1	3609	`67ab8dd4ed25627860374afc6d28449d7b0be22e281f154616a254717c5d63b9`

Original observations, retained as history:

The original run/job status snapshots and HTTP failure observations are retained. The paired original CI 75 succeeds from complete logs. The signed source also passes its required local strict Rust, native-build, documentation and formatting checks. Those results do not replace the missing original CI evidence. Do not attribute this to a source regression without the original failure output.

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 74](https://git.erikinkinen.fi/erix/inputd/actions/runs/74) (attempt 2), [CI 75](https://git.erikinkinen.fi/erix/inputd/actions/runs/75) (attempt 1), pass at unchanged commit `ed6473c6e741b1c3b8049f2dffb2a959c475c5ac`. All four test/Markdown job logs are complete and hashed (62,791 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 inputd CI reports failed jobs whose log endpoints return HTTP 500. The missing logs prevent diagnosis and complete CI acceptance for the selected source. The cause of either the job failures or log-service errors is not established. ## Reproduction Inspect [CI 74](https://git.erikinkinen.fi/erix/inputd/actions/runs/74) at the original selected commit, then request the original job logs with an authorized Forgejo API client: - `GET /api/v1/repos/erix/inputd/actions/jobs/21213/logs?attempt=1` → HTTP 500. - `GET /api/v1/repos/erix/inputd/actions/jobs/21214/logs?attempt=1` → HTTP 500. Each listed request returned HTTP 500 in the retained terminal-status observation on 18 September 2026. At that original observation the workflows had not been rerun or cancelled. ## Expected and actual behavior Expected: every terminal job exposes its complete original log, including the failure and cleanup outcome. Actual: Forgejo reports failure for the selected jobs but returns HTTP 500 for their logs. No complete log, warning count or code-level failure cause can be inferred for those jobs. ## Environment and identity - Repository: `inputd` at `ed6473c6e741b1c3b8049f2dffb2a959c475c5ac` on `feature/posix-compat`. - Execution: original Forgejo push/PR workflows and the job-attempt selectors above. - Image/VM: these are component validation jobs; no guest outcome is inferred. - Toolchain/runtime details for the missing jobs: unavailable until their original logs are recovered. - Last known working revision for log retrieval: not established. ## Evidence and prior checks Verified rerun evidence: | Workflow | Job | Attempt | Complete log bytes | SHA-256 | | --- | --- | --- | --- | --- | | 74 | 21213 | 2 | 27786 | `cd7fff7e9a0abb84b3b8cbe238a1b03b45229b7ecc6f253cd0b192b350616da1` | | 74 | 21214 | 2 | 3601 | `855081b4a2895958ac89051028b9ccf429b4e4e74be38299c584ccb709b18572` | | 75 | 21215 | 1 | 27795 | `4b313fdc87bb55812fc77671bd08c11d19371bb983cc692320792ffc18961bc0` | | 75 | 21216 | 1 | 3609 | `67ab8dd4ed25627860374afc6d28449d7b0be22e281f154616a254717c5d63b9` | Original observations, retained as history: The original run/job status snapshots and HTTP failure observations are retained. The paired original CI 75 succeeds from complete logs. The signed source also passes its required local strict Rust, native-build, documentation and formatting checks. Those results do not replace the missing original CI evidence. Do not attribute this to a source regression without the original failure output. ## Tracking [Feature issue 1](https://git.erikinkinen.fi/erix/inputd/issues/1), [PR 2](https://git.erikinkinen.fi/erix/inputd/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-18 09:07:44 +02:00

erikinkinen referenced this issue

2026-09-18 09:07:45 +02:00

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

erikinkinen referenced this issue

2026-09-18 09:07:45 +02:00

WIP: Align signed runtime dependencies #2

erikinkinen closed this issue