System.BadImageFormatException for VSTest@2 task in agent version 3.240.1

[genedodge]

Description

On release of agent version 3.240.1, builds started failing for a pipeline that uses the VSTest@2 task.

This release may or may not be the cause?

Platforms affected

• [X] Azure DevOps
• [ ] GitHub Actions - Standard Runners
• [ ] GitHub Actions - Larger Runners

Runner images affected

• [ ] Ubuntu 20.04
• [ ] Ubuntu 22.04
• [ ] Ubuntu 24.04
• [ ] macOS 11
• [ ] macOS 12
• [ ] macOS 13
• [ ] macOS 13 Arm64
• [ ] macOS 14
• [ ] macOS 14 Arm64
• [ ] Windows Server 2019
• [X] Windows Server 2022

Image version and build link

20240610.1.1 https://github.com/actions/runner-images/releases/tag/win22%2F20240610.1

Is it regression?

Agent version 3.239.1 did not exhibit this issue

Expected behavior

Tests are run and coverage is collected

Actual behavior

Fails with error: #[error]Data collector 'Code Coverage' message: Data collector caught an exception of type 'System.BadImageFormatException': 'Image is too small.'. More details: ..

Repro steps

Add VSTest@2 task to yaml build pipeline and run on agent 3.240.1 to see the error

Exact task in affected pipeline is:

  - task: VSTest@2
    displayName: 'Run Unit Tests'
    inputs:
      testAssemblyVer2: |
       **\*Test.Unit.dll
       **\*Tests*
       !**\obj\**
      vsTestVersion: latest
      runInParallel: false
      codeCoverageEnabled: true
      platform: '$(BuildPlatform)'
      configuration: '${{parameters.buildConfiguration}}'
      runSettingsFile: './coverage.runsettings'

[hemanthmanga]

@genedodge Thank you for bringing this issue to us, we are investigating on this issue and we will update you on this issue after our findings.

[jonadv]

Also had this issue, it seems related to this checkbox of Visual Studio Test

unchecking that box made the pipeline complete

[hemanthmanga]

@jonadv

Please enable code coverage checkbox as mentioned in the above screenshot.

[hemanthmanga]

@jonadv could please provide your comments.

[jonadv]

@hemanthmanga sorry, dont have the time to test this in our environment or share logs. i just meant it as an indication for people looking into this once it is fixed, we can turn it back on again and see if it works

same goes for my comment here

[fhnaseer]

This has been fixed and will be available in vstest 17.11 release.

[hemanthmanga]

@genedodge @jonadv We have verified the same as per the issue , It got fixed with 17.11 release[Vstest], closing this issue, Thank you.