search

artilleryio / artillery

The complete load testing platform. Everything you need for production-grade load tests. Serverless & distributed. Load test with Playwright. Load test HTTP APIs, GraphQL, WebSocket, and more. Use any Node.js module.
https://www.artillery.io
Mozilla Public License 2.0
8.05k stars 512 forks source link

Artillery test on Azure ACI failed to conclude #3355

Open mmathoosh opened 1 month ago

mmathoosh commented 1 month ago

Infrastructure for the Azure run-aci was prepared and tests were running (engine: playwright). Which is also visible in the https://app.artillery.io/. Up to the moment when tests are finished everything seem to work fine.

Version info: 

<"^2.0.20",>

Running this command: 

"artilleryRunInAzure": "artillery run-aci --variables \"{\\\"passwordPerfTest\\\": \\\"xxxx\\\"}\" xxxx.yml --record --key xxxxxx --tenant-id xxxxxx --subscription-id xxxxxxx --storage-account artillexxxaccount --blob-container artilleryxxxblobcontainer --resource-group xxx --region northeurope --count 1"

I expected to see this happen:

at the end of the tests I'd expect that test is finalized

Instead, this happened:

test stays in the stage on the picture image image

mmathoosh commented 1 month ago

Additional information: "Page performance" metrics are not uploaded during/after the test run to the artillery.app.io image

hassy commented 1 month ago

thank you @mmathoosh, we'll look into it. In the second screenshot - is that from a different test?

mmathoosh commented 1 month ago

thank you @mmathoosh, we'll look into it. In the second screenshot - is that from a different test?

if you mean screenshot from comment, yes it is different test. I have suspicion something from these steps failed:

  1. Collect logs and metrics from running container groups and aggregate and print reports (also missing in the container)
  2. Delete AQS queue, files uploaded to ABS, and ACI container groups when the test is finished
hassy commented 1 month ago

@mmathoosh we'll need more details to try to debug what might have gone wrong. Would you mind dropping me an email on hveldstra@artillery.io or sending a message via the chat widget in the Artillery Cloud dashboard? Would like to fix this asap