[BUG] test execution errors with Run stopped Criteria not validated when waitForCompletion is set to false
@mohitpavan is already working on this.
Since May 13, 2026.
Assessment
This issue has not been assessed yet.
Description
Describe the bug
When setting waitForCompletion to false test execution is failing with Run stopped
Criteria not validated, there is no logs in azure load testing to indicate what criteria is not validated. If I manually click rerun in azure load testing for that test run, it fires off another test execution that runs as expected.
To Reproduce
set waitForCompletion is false in github action parameters
Run azure/load-testing@91cc816f79b6b2a96b73ee130ceadf42d764c4b3
with:
loadtestConfigFile: ./loadtesting/AzureConfig/****
loadtestResource: *****
resourceGroup: *****
waitForCompletion: false
Test '****' already exists
Deleting 1 existing test file(s) which is(are) not in the configuration yaml file.
Uploading the user properties file
Uploaded user properties file for the test successfully.
Uploading the test script file
Uploaded test script file for the test successfully.
Validation status of the test plan: VALIDATION_SUCCESS
Validated test plan for the test successfully.
Updated server metrics successfully
Creating and running a testRun for the test
Creating and running a testRun for the test
View the load test run in Azure portal by following the steps:
- Go to your Azure Load Testing resource '' in subscription ''
- On the Tests page, go to test '*****'
- Go to test run '*****'
Test run started. Not waiting for completion as per input.
Result: Test Run Started Successfully.
Test run is provisioned and stops immediately with message 'Run stopped
Criteria not validated'
Expected behavior
When waitForCompletion is to false it should kick off a test run that does not error out
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: Windows 11
- Browser: edge
- Version: 147.0.3912.60
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 27
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 8
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/load-testing
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Azure/load-testing#166 · 1 comment · 1 reaction ·
-
Upgrade to node 24 Openneed-to-triage
Azure/load-testing#162 · 6 comments · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/load-testing#48 · 2 comments ·
-
need-to-triage
Azure/load-testing#47 · 1 assignee ·
-
need-to-triage
Azure/load-testing#46 · 1 assignee ·
All issues in Azure/load-testing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·