Iman Biglari

@jakubch1 so if I add `/PROFILE` to linker options, code coverage will automatically use static instrumentation instead of dynamic instrumentation? If not, how do I instruct test host to use...

@jakubch1 I'm afraid adding `/PROFILE` did not fix the issue. Logs attached [vstestlog.datacollector.24-01-20_23-20-38_09648_4.log](https://github.com/microsoft/vstest/files/13999494/vstestlog.datacollector.24-01-20_23-20-38_09648_4.log) [vstestlog.host.24-01-20_23-20-51_39345_4.log](https://github.com/microsoft/vstest/files/13999495/vstestlog.host.24-01-20_23-20-51_39345_4.log) [vstestlog.log](https://github.com/microsoft/vstest/files/13999496/vstestlog.log) Linker command line as extracted from build pipeline logs: `Link: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.37.32822\bin\HostX86\x86\link.exe /ERRORREPORT:QUEUE...

@jakubch1 Even after updating `.runsettings` I am seeing the same behaviour. > > Please try to configure below flags in runsettings: > > ``` > True > False > ```...

@jakubch1 Sorry forgot to attah [vstestlog.log](https://github.com/microsoft/vstest/files/14015075/vstestlog.log) [vstestlog.datacollector.24-01-22_08-10-45_20726_4.log](https://github.com/microsoft/vstest/files/14015076/vstestlog.datacollector.24-01-22_08-10-45_20726_4.log) [vstestlog.host.24-01-22_08-11-01_73850_4.log](https://github.com/microsoft/vstest/files/14015077/vstestlog.host.24-01-22_08-11-01_73850_4.log)

@jakubch1 Added `runSettingsFile` to `VSTest@2` task, double checked the pipeline execution log. ``` . . . ########################################################################## DtaExecutionHost version 19.229.34210.1. Starting TestExecution Model... Result Attachments will be stored in LogStore...

@jakubch1 No joy. Still seeing the crash. Logs attached. Also, not sure what you mean by instrumenting only 1 file? Our test project is `IntegrationTests,dll` and pipeline console reflects this:...

@jakubch1 I find that hard to believe, as I can see code coverage in SonarCloud. However, I will try and get back to you.

@jakubch1 Turning off code coverage leads to successful execution of the test. Logs attached [vstestlog.log](https://github.com/microsoft/vstest/files/14052332/vstestlog.log) [vstestlog.datacollector.24-01-25_02-45-39_84177_4.log](https://github.com/microsoft/vstest/files/14052329/vstestlog.datacollector.24-01-25_02-45-39_84177_4.log) [vstestlog.host.24-01-25_02-45-55_30456_4.log](https://github.com/microsoft/vstest/files/14052333/vstestlog.host.24-01-25_02-45-55_30456_4.log)

@jakubch1 I'm afraid I had a crash with all four set to false. [vstestlog.datacollector.24-01-26_10-07-10_50220_4.log](https://github.com/microsoft/vstest/files/14063439/vstestlog.datacollector.24-01-26_10-07-10_50220_4.log) [vstestlog.host.24-01-26_10-07-13_39508_4.log](https://github.com/microsoft/vstest/files/14063440/vstestlog.host.24-01-26_10-07-13_39508_4.log) [vstestlog.log](https://github.com/microsoft/vstest/files/14063441/vstestlog.log)

@jakubch1 Yes we set a mutex and wait for a thread to terminate... That's one of the log messages from the test routine. Why?