From c694fc93f786629b52b1edb907d868c03f8f0351 Mon Sep 17 00:00:00 2001 From: "Claude (noether)" Date: Thu, 23 Jul 2026 12:42:22 +0200 Subject: [PATCH] =?UTF-8?q?ci:=20unblock=20sic=20jobs=20=E2=80=94=20sicd-a?= =?UTF-8?q?rch=20needed=20a=20job=20on=20the=20DEAD=20debian-aarch64=20run?= =?UTF-8?q?ner?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The four sic jobs (sicd/sic-agent x arch/debian, all runs-on arch-aarch64) have NEVER run since they were added 2026-07-19. Root cause: sicd-arch (head of the chain) had needs: daedalus-v4l2-dkms-debian -- a job on the debian-aarch64 runner (bohr), which is offline/unregistered. Every debian-aarch64 job skips, so sicd-arch was blocked forever, cascading to the whole sic chain. The dependency was spurious (sic has nothing to do with a v4l2 DKMS build); it only existed to serialize on the single arch runner, but was pinned to the wrong chain tail. Re-point to reauktion-home-ca-debian (a leaf on the WORKING arch-aarch64 runner) -- same serialization discipline, off the dead runner. Upstream keeps continue-on-error, so sic runs regardless of that job's result. This is what let 0.2.0 (and every prior sic push) silently publish nothing. Co-Authored-By: Claude Opus 4.8 --- .gitea/workflows/build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitea/workflows/build.yml b/.gitea/workflows/build.yml index a9f5b781b..c2cd4638e 100644 --- a/.gitea/workflows/build.yml +++ b/.gitea/workflows/build.yml @@ -1742,7 +1742,7 @@ jobs: # =========================================================================== sicd-arch: - needs: daedalus-v4l2-dkms-debian + needs: reauktion-home-ca-debian runs-on: arch-aarch64 steps: - uses: actions/checkout@v4