I am at the point with this issue thinking that a powershell script is being executued on my Master during a Distributed run. This powershell script is from the Team City side and may be a script trying to take down the job due to something Team City detected.
I am testing out a ADO pipeline doing a Distributed run to the same slaves.
More info to come after this testing is done.
Current Status as of June 10, 2021
Running a Team City job that kicks off Distributed Testing and now using an ADO pipeline to kick off the same commandline
for Distributed Testing, the issue of the script run ending\stopping at some random time is still occurring.
My suspensions now is maybe how Hyper-V works ?
Session load balancing, networking connection break, or something else that could be affecting the Master and somehow killing my Slaves running scripts.
Some anomaly is affecting my Master to trigger a stop to my Slaves and I cannot figure this one out still.
I was hoping the issue was more Team City related, but that is not the case now.
