search

Azure / load-testing

Automate azure load test through github actions
MIT License
17 stars 17 forks source link

[BUG] Tests fail to start with cli issue #95

Closed cmyllis closed 2 weeks ago

cmyllis commented 3 weeks ago

Describe the bug When triggering the tests from our github actions we started getting this error. An error occurred while getting credentials from Azure CLI: Error: spawn EINVAL at ChildProcess.spawn (node:internal/child_process:421:11) at spawn (node:child_process:761:9) at execFile (node:child_process:351:17) at C:\gh-performancetests\_work\_actions\azure\load-testing\v1.1.23\lib\mappers.js:378:42 at new Promise (<anonymous>) at C:\gh-performancetests\_work\_actions\azure\load-testing\v1.1.23\lib\mappers.js:377:16 at Generator.next (<anonymous>) at C:\gh-performancetests\_work\_actions\azure\load-testing\v1.1.23\lib\mappers.js:31:71 at new Promise (<anonymous>) at __awaiter (C:\gh-performancetests\_work\_actions\azure\load-testing\v1.1.23\lib\mappers.js:27:12)

To Reproduce Steps to reproduce the behavior: Not sure but happens each time for us

Expected behavior For the tests to be triggered.

Screenshots image

ninallam commented 2 weeks ago

@cmyllis Thanks for reaching out. We will check the issue and get back.

mohitpavan commented 2 weeks ago

https://github.com/nodejs/node/issues/52554 there is an issue with a nodemodule in windows this is a breaking change, fix will be up by today EOD. @ninallam FYI

mohitpavan commented 2 weeks ago

the fix is deployed now. please let us know if you stil lface the issue, we were able to repro the issue and fixed and able to see the issue to be fixed too. closing the issue assuming its fixed for cx too.