MSTestV2 update will not execute C++ tests using default runsettings

Note

Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo

For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

If you have an issue or request for the Azure Pipelines service, use developer community instead:

https://developercommunity.visualstudio.com/spaces/21/index.html )

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: VsTestV2

Environment

• Server - Azure Pipelines or TFS on-premises? Azure Pipelines

• Agent - Hosted or Private: Private - Windows 10 - 2.150.3

Issue Description

Our VSTestV2 task updated to 2.160.2 from 2.159.1. Since then, C++ Unit tests will not execute. Error:

##[error]The active test run was aborted. Reason: Test host process crashed

I have filtered this down to the CodeCoverage node in the default generated runsettings file, which have changed from:

    <Sources>
        <Exclude>
            <Source>.*\\atlmfc\\.*</Source>
            <Source>.*\\vctools\\.*</Source>
            <Source>.*\\public\\sdk\\.*</Source>
            <Source>.*\\microsoft sdks\\.*</Source>
            <Source>.*\\vc\\include\\.*</Source>
        </Exclude>
    </Sources>

to:

    <Sources>
        <Exclude>
            <Source>.*\atlmfc\.*</Source>
            <Source>.*\vctools\.*</Source>
            <Source>.*\public\sdk\.*</Source>
            <Source>.*\microsoft sdks\.*</Source>
            <Source>.*\vc\include\.*</Source>
        </Exclude>
    </Sources>

Rolling back to the previous sources exclusions allows the tests to run.

Task logs

[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]

Troubleshooting

Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Error logs

[Insert error from the logs here for a quick overview]

[goozdev]

We have faced the same issue, since the auto-upgrade from 2.159.1 to 2.160.2. Using the original .runsettings with ‘\\’ we solved the issue for us.

See related issue: https://github.com/microsoft/azure-pipelines-tasks/issues/11750

[Lawls91]

Nevermind, figured this out. Previously I had codecoverage enabled, which was the part that caused the issue. When I checked in a runsettingsfile, I disabled codecoverage in the task which no longer generates that block.

Closing as fixed