From f39ed1684b3056063c691bf8c436f641c56daeb1 Mon Sep 17 00:00:00 2001 From: Sebastian Date: Sat, 3 Oct 2026 19:43:30 +0200 Subject: [PATCH] Sequence windows after build to avoid shared action-cache race Run 136's build job failed immediately (not a segfault) because it and windows both clone actions/checkout@v4 and actions/cache@v4 into the same cache directory on the runner at the same time; one job's git fetch loses the race and ends up with a missing dist/index.js. needs: build serializes them so they don't race on that shared cache. Co-Authored-By: Claude Sonnet 5 --- .gitea/workflows/gitea-build.yaml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/gitea-build.yaml b/.gitea/workflows/gitea-build.yaml index 1812398..8f5d7cc 100644 --- a/.gitea/workflows/gitea-build.yaml +++ b/.gitea/workflows/gitea-build.yaml @@ -33,8 +33,14 @@ jobs: - name: Build run: just release - # Cross-compiles for Windows so link breakages show up before a release + # Cross-compiles for Windows so link breakages show up before a release. + # Runs after `build`: both jobs clone the same cached actions/checkout and + # actions/cache repos into one shared directory on the runner, and starting + # them at the same time can race on that clone/fetch - one job then gets a + # missing or corrupted action and fails immediately (seen on run 136, not + # related to the odin test fix above). Sequencing avoids the race. windows: + needs: build runs-on: ubuntu-latest steps: - name: Checkout Repository