CI runner failures prevent validation of every branch #30

Open
opened 2026-08-03 10:11:36 -04:00 by logikoma · 0 comments
Collaborator

CI reports failures on every current branch, including PR #29, despite successful local reproductions. This tracking issue is for the runner or workflow; it is not a requested change to PR #29.

Evidence

  • Run 8 at 23ccb66 (2026-07-31) was the last run where cmake_build, sanitizers, and mutation_test passed.
  • No job has passed on any run since run 9 at 812d846 (2026-08-01), across main and all subsequently pushed branches.
  • akgl_build and coverage have failed on every run in which they appeared, including runs 2 through 8.
  • PR #29 head 3342f2b succeeds locally with the workflow build and test steps: standard build/tests (112/112) and ASan/UBSan build/tests (112/112, no sanitizer report).
  • The pinned deps/libakgl (bbb7b8f) and deps/basicinterpret (d76162c) submodule commits fetch anonymously, so submodule reachability is not the failure.
  • Available Actions API diagnostics are insufficient: the run-jobs endpoint returns an empty job list and job-log requests return 404.

Required outcome

Restore reliable CI job execution and make the failing step and its logs available to repository contributors. Re-run the workflow against an unchanged commit to confirm that green/red status once again reflects the submitted change.

Linked from PR #29.

CI reports failures on every current branch, including PR #29, despite successful local reproductions. This tracking issue is for the runner or workflow; it is not a requested change to PR #29. ## Evidence - Run 8 at `23ccb66` (2026-07-31) was the last run where `cmake_build`, `sanitizers`, and `mutation_test` passed. - No job has passed on any run since run 9 at `812d846` (2026-08-01), across `main` and all subsequently pushed branches. - `akgl_build` and `coverage` have failed on every run in which they appeared, including runs 2 through 8. - PR #29 head `3342f2b` succeeds locally with the workflow build and test steps: standard build/tests (112/112) and ASan/UBSan build/tests (112/112, no sanitizer report). - The pinned `deps/libakgl` (`bbb7b8f`) and `deps/basicinterpret` (`d76162c`) submodule commits fetch anonymously, so submodule reachability is not the failure. - Available Actions API diagnostics are insufficient: the run-jobs endpoint returns an empty job list and job-log requests return 404. ## Required outcome Restore reliable CI job execution and make the failing step and its logs available to repository contributors. Re-run the workflow against an unchanged commit to confirm that green/red status once again reflects the submitted change. Linked from PR #29.
Sign in to join this conversation.