From ab60acd9f41ed89e0f195a2b4198fb05627ee485 Mon Sep 17 00:00:00 2001 From: Markus Fritsche Date: Wed, 20 May 2026 15:52:40 +0200 Subject: [PATCH] build.yml: runs-on debian-aarch64 (label, not runner name) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 5feab57 set runs-on to actrunner-debian-aarch64-bohr, which is the display name of the bohr runner, not a label. Gitea Actions matches runs-on against labels — the actual labels on bohr are debian-trixie, aarch64, debian-aarch64. Using the runner-name as runs-on leaves the job unrouted (no matching runner). --- .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 86ed67383..b30dd73b2 100644 --- a/.gitea/workflows/build.yml +++ b/.gitea/workflows/build.yml @@ -976,7 +976,7 @@ jobs: # __vaDriverInit_1_23, which trixie's libva 2.22 runtime cannot bind: the # .deb installed but vaInitialize() returned -1 on every host. A native # trixie runner avoids the cross-distro ABI skew entirely. - runs-on: actrunner-debian-aarch64-bohr + runs-on: debian-aarch64 continue-on-error: true steps: - uses: actions/checkout@v4 -- 2.47.3