I'm not sure how to do this exactly!
Do I have to create a .CMD in my repo and somehow call it from yml script?
What would be the content of that file to ensure sequential run and how do
I call it from yml?
Yea, I had been changing it from cmd to ps to pwsh and to sh just to get the thing working!
That's correct, the main thread is in charge of running each new thread assigned to a specific test.
I do not get any error when --test-threads=1 locally. Not having it actually causes errors which are different every time. The web-server mocker in tests only listens on port 1234 and if multiple tests are run it will cause issue since it has a fixed response.
Yes, I have tested it with multiple versions as well
I have 6 cores at my local machine
How can I echo the command that test_script actually calls/runs?
And in what env./shell the .yml runs/launches its command?
CMD is being called by build agent (.NET program) using native interop calls. What you see in the line before command like here is exact echo of what is going to be called.
RDP to build VM and run command manually so you can rule out the fact that command is being called by build agent. Please note that RDP session does not have the same environment variables as build session, so you need to re-create environment variables which are critical for this command execution.