Flaky tests

[nohwnd]

[Evangelink]

macos keeps getting flaky too

[nohwnd]

do you know which tests?

[Evangelink]

Sorry I haven't looked at the failure. It was on the 2 arcade PRs. Somehow I cannot access the build (maybe I no longer have some permissions).

[nohwnd]

ok, let me know if you have a concrete build you cannot access so we can debug it and give you permissions if that is the problem.

[nohwnd]

[nohwnd]

ubuntu

[nohwnd]

unit tests are flaky because of processor resources being low, I can repro on wsl when reducing the allowed cpus to 2 (what azdo gives the pipeline)

Or locally to 1 cpu on windows and running till failure in VS.

# limit cpus and watch the processes to make sure we did it right, takes 3-4 runs to fail
get-process -Name DevHub | % { $_.ProcessorAffinity = 0b1 }; 1..100 | % { get-process *vstest*unit* | select name, processoraf* ; start-sleep -seco 0.5 }

[nohwnd]

[nohwnd]

The affinity also kills your editor experience, so restart VS after (or restore affinity to full).

[nohwnd]

no local repro :/

[Evangelink]

@nohwnd images are not loading for me.

[nohwnd]

weird, I can re-screenshot it and post it again. Oh wait.

Coverage parallell - probably solved by the run handler actually being thread safe now.
StartShouldShowProgressMessage - can repo locally on 1cpu computer
executorInitialize*OverRunSettings - can repro locally on 1 cpu computer
runTestswithcustomtesthostlauncher - not sure I saw that recently

[nohwnd]

I can see the images on a different device, so not a me problem hopefully.