Hassy Veldstra

Isn't the match failing because `code` in the response is `400` but the `match` expression expects it to be `200`?

hi @artieghosh99 👋 The custom JS looks good. Can you check to make sure that the file is called `send50mbTiff.js` and that it's in the same directory as the Artillery...

hey @jakekgrog 👋 Unable to reproduce here either. Are you using an npm caching proxy or a private registry of any kind (e.g. Verdaccio, Artifactory, Cloudsmith etc)

Try changing `npx playwright install` to `npx [email protected] install`. Artillery's Playwright integration uses Playwright v1.37.1 ([source](https://github.com/artilleryio/artillery/blob/main/packages/artillery-engine-playwright/package.json#L14)), and browsers in Playwright need to be installed for specific versions.

Or better yet: run your tests on AWS Fargate ([docs](https://www.artillery.io/docs/load-testing-at-scale/aws-fargate)). That will let you generate more load (GitHub Actions is not a great place to actually execute the tests from),...

Going to add more context here for anyone running into similar issue and trying to debug. (Information is accurate at the time of writing and will probably go out of...

@lazzarello glad it's working now!

Hi @oliver-jenny 👋 An ARM version is something we'll add. Just curious - is there a particular reason you prefer running Artillery in Docker vs installing it directly with `npm`?

yes, we try to address any reported dependency vulnerabilities in each release so we’ll try to upgrade this one in the upcoming release On Thu, 2 May 2024 at 08:51...

thanks @thrandale! Is the issue due to a missing relative path? ie. in your example `./artilleryRunner.mjs` should work as expected (if the MJS file is in the same directory as...