You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Smoke tests failing in stage 2 with VSTESTTASK2 error #4003
This may be a regression caused by microsoft/vstest#4834. These tests were working last Friday and failing today after incorporating changes that included microsoft/vstest#4834. @nohwnd - Can you take a look?
Here's a binlog: BuildTests_0122193259.zip. We need to get this resolved soon for .NET 9 Preview 1.
This is more likely linked to this change: https://github.com/dotnet/sdk/pull/38098/files which changes how failed tests are reported to take advantage of msbuild terminal logger which is now the default experience for dotnet build.
I am trying to repro to see if the smoke tests failed and VSTEST fails to report the details of the failure. Or if VSTEST is failing and the change needs to be reverted.
I can run the tests but I always get the full output of the error. And I can't run tests without failures locally because I don't have all the artifacts. I always see: Tarball path '' specified in does not exist. ( from here ) I downloaded what I could but I still cannot get it to work locally.
I can see in binary logger the same error output as in build, but it is followed by the actual error message.
In your run I cannot see any failures in trx, so I am not sure where the errors are coming from and if they are real.
Activity
mthalman commentedon Jan 22, 2024
This may be a regression caused by microsoft/vstest#4834. These tests were working last Friday and failing today after incorporating changes that included microsoft/vstest#4834. @nohwnd - Can you take a look?
Here's a binlog: BuildTests_0122193259.zip. We need to get this resolved soon for .NET 9 Preview 1.
mthalman commentedon Jan 23, 2024
I ran a test build (internal link) that reverted the change from microsoft/vstest#4834 but that didn't help at all.
nohwnd commentedon Jan 23, 2024
This is more likely linked to this change: https://github.com/dotnet/sdk/pull/38098/files which changes how failed tests are reported to take advantage of msbuild terminal logger which is now the default experience for
dotnet build.I am trying to repro to see if the smoke tests failed and VSTEST fails to report the details of the failure. Or if VSTEST is failing and the change needs to be reverted.
nohwnd commentedon Jan 23, 2024
Running another test build with opt-out from the new feature https://dev.azure.com/dnceng/internal/_build/results?buildId=2360131&view=results
In the meantime I am trying to repro locally.
nohwnd commentedon Jan 23, 2024
I can't repro fully.
I can run the tests but I always get the full output of the error. And I can't run tests without failures locally because I don't have all the artifacts. I always see:
Tarball path '' specified in does not exist.( from here ) I downloaded what I could but I still cannot get it to work locally.I can see in binary logger the same error output as in build, but it is followed by the actual error message.
In your run I cannot see any failures in trx, so I am not sure where the errors are coming from and if they are real.
I've edited the target to actually propagate the opt-out flag and started another build here (from a new branch, I want to see how the other one will finish) https://dev.azure.com/dnceng/internal/_build/results?buildId=2360247&view=results
MichaelSimons commentedon Feb 1, 2024
[Triage] closing as is appears this fix flowed in.