-
Notifications
You must be signed in to change notification settings - Fork 538
Description
Bug Summary: After executing an artillery playwright test using Azure ACI, the test will run for the specified duration. Once completed, the container instances will throw a 413 Rest Error. This is preventing the execution of larger/longer tests because the worker container instance is limited by the Azure Service Queue hard limit of 64 KB of message size.
There is no way to limit the metrics being recorded in the workers, which causes this error to always occur when attempting to run tests with more concurrent users.
Version info:
Artillery: 2.0.22
Node.js: v22.13.1
OS: win32
Playwright: 1.49.1
Running this command:
artillery run-aci artillery.yml --quiet --name test1 --client-id fakeclientId --client-secret fakeClientSecret --tenant-id fakeTenantId --subscription-id fakeSubscriptionId --storage-account fakeAcctName --blob-container fakeContainer --resource-group fakeResourceGroup --region xxxxxxxxxxxxxx --count 5 --memory 15 --cpu 8 --output artillery.json
I expected to see this happen:
When executing the command, the container instances get created and execute the test. After test execution, the Azure test artifacts are cleaned up and the json file is created on the control machine.
Instead, this happened:
When executing the command, the container instances get created and execute the test. After test execution, the Azure test artifacts are not cleaned up. The logs in the container instances show the 413 error. The control machine test execution does not exit.
Files being used:
[RestAPI_Error.txt](https://github.com/user-attachments/files/19394648/RestAPI_Error.txt)
[artillery.yml.txt](https://github.com/user-attachments/files/19394749/artillery.yml.txt)
[login.ts.txt](https://github.com/user-attachments/files/19394827/login.ts.txt)