Closed iansul closed 7 months ago
It's hard to know, given that it works locally for you (and me as well, just using dotnet new xunit
and "downgrading" the generated project to .NET 6). If this didn't work, the .NET team would've in contact, since they use xUnit.net as well, and they're using Azure Pipelines as well (I see tons of their builds on GitHub PRs showing up with Azure Pipelines icons/links, like this one which has results on Azure Pipelines. Many of those are running on Linux.
I'm assuming the failing project you have is a closed source project. Is it possible to trim down to a repro that could be shared?
Thanks for the follow up @bradwilson I will see if I can get a minimal repro.
Closing for lack of response. Please open a new issue if this is still a problem. Thanks!
I have a Test project that tests a Project that produces a NuGet package that targets net472 and net6.0. It properly tests both Net 4.7.2 and Net 6.0 locally, but when I try to run the tests in an ADO pipeline it fails to run the net6.0 target with the error:
I can't figure out which diagnostic logs I should look in. And I can't find the "testhost.deps.json" file anywhere in my local build to see what's in it and maybe tell me where I could look for it in the ADO build to see if it's different.
The net4.7.2 target completes successfully:
Does this have anything to do with trying to run the pipeline on an ubuntu image? My pipeline doesn't specify a pool so it's getting the default from Azure Pipelines Pool which seems to be ubuntu.
Not sure if this is related but I'm also trying to capture code coverage with coverlet.