From 45f23a870efce8967273983c8c0df0e52311ade3 Mon Sep 17 00:00:00 2001 From: Matthias Linhuber Date: Thu, 27 Aug 2026 17:33:10 +0200 Subject: [PATCH] fix(ci): run artillery from node_modules instead of the broken action #38 fixed the first of two things wrong with this job - apt failing on an unreachable Microsoft mirror - and that is now on main. With that out of the way the job gets one step further and hits the second: the container behind artilleryio/action-cli@v1 no longer has a working entrypoint, so the step dies with `/home/node/artillery/bin/run: not found` before the scenario starts. artillery ^2.0.24 is already a devDependency and npm ci has run by this point, so npx artillery run does the same work without the container. The job has been red since May; neither failure is a test failure. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01QLGHEpzx7D9NYHx4fCmHa9 --- .github/workflows/artillery-tests.yml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.github/workflows/artillery-tests.yml b/.github/workflows/artillery-tests.yml index f7f7d63..9798012 100644 --- a/.github/workflows/artillery-tests.yml +++ b/.github/workflows/artillery-tests.yml @@ -26,7 +26,9 @@ jobs: run: sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list /etc/apt/sources.list.d/azure-cli.list - name: Install Playwright Browsers run: npx playwright install --with-deps chromium + # artilleryio/action-cli@v1 runs a container whose entrypoint no longer + # resolves (`/home/node/artillery/bin/run: not found`), so the step fails + # regardless of the test. artillery is already a devDependency here, so + # run it straight from node_modules and drop the broken action. - name: Execute load tests - uses: artilleryio/action-cli@v1 - with: - command: run tests/ide/scalable/artillery/Artillery.ts + run: npx artillery run tests/ide/scalable/artillery/Artillery.ts