From b5e281df630b013d2196855b7186600b8a430cc0 Mon Sep 17 00:00:00 2001 From: David Anthoff Date: Wed, 19 Aug 2026 10:49:34 -0700 Subject: [PATCH] Forward max-workers to julia-run-testitems MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `julia-run-testitems` has had a `max-workers` input all along, but this workflow never passed one through, so a repository using it has no way to bound the number of test processes — even though its four siblings (`threads`, `gc-between-testitems`, `memory-threshold`, `schedule`) are all forwarded. DebugAdapter.jl needs it: on Julia 1.0 there is no precompile cache locking, and on Windows a `.ji` file that another process holds open cannot be replaced, so as soon as that package has more than one test item the processes race and whichever loses reports `Cannot write cache file`. --- .github/workflows/juliaci.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/juliaci.yml b/.github/workflows/juliaci.yml index 570ae90..84909c9 100644 --- a/.github/workflows/juliaci.yml +++ b/.github/workflows/juliaci.yml @@ -91,6 +91,10 @@ on: type: string required: false default: "" + max-workers: + type: string + required: false + default: "" threads: type: string required: false @@ -549,6 +553,7 @@ jobs: junit-path: ${{ inputs.junit-path }} coverage-lcov-path: ${{ inputs.coverage-lcov-path }} output-mode: ${{ inputs.output-mode }} + max-workers: ${{ inputs.max-workers }} threads: ${{ inputs.threads }} gc-between-testitems: ${{ inputs.gc-between-testitems }} memory-threshold: ${{ inputs.memory-threshold }}