After starting test from UI, state shows as STOPPED even though it's running
See original GitHub issueDescribe the bug
After starting test from UI, state shows as STOPPED
even though it’s running.
If I click start again, then the status is updated to SPAWNING
correctly
Expected behavior
Status should show as “SPAWNING” I believe.
Steps to reproduce
Just start test from UI.
Environment
- OS: k8s
- Locust version: 1.2.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:17 (11 by maintainers)
Top Results From Across the Web
Tests not running in Test Explorer - visual studio
All tests are running, all tests are showing the right test outcome. However, the tests are not running when using the Visual Studio...
Read more >X apps running in WSL randomly stop displaying on X Server ...
Start the Debian WSL app using the icon created when Debian installed. ping hostip (192.168.xx.32 in my case) to confirm. It works.
Read more >Run tests | IntelliJ IDEA Documentation - JetBrains
After that, the test will be suspended, allowing you to examine its current state. You can step through the test to analyze its...
Read more >Troubleshoot pipeline runs - Azure DevOps - Microsoft Learn
If a pipeline doesn't start at all, check the following common trigger related issues. UI settings override YAML trigger setting; Pull request ...
Read more >Save UI states - Android Developers
When the user's expectations about UI state do not match default system behavior, you must save and restore the user's UI state to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m in a good position to debug it myself but thought I’d post an issue in case others had the same problem.
Hmm got debug logs from today but doesn’t look like they help much:
🤔