Microsoft.DotNet.Cli.Test.Tests.GivenDotnetTestBuildsAndRunsTestFromCsproj.PathEndsWithSlashOrBackslash exhibits consistent failure in many branches:
https://helixr1107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-sdk-refs-pull-54031-merge-40db291649ad4a27ad/dotnet.Tests.dll.9/1/console.3fe54d0c.log?helixlogtype=result&skoid=8eda00af-b5ec-4be9-b69b-0919a2338892&sktid=72f988bf-86f1-41af-91ab-2d7cd011db47&skt=2026-05-06T16%3A55%3A12Z&ske=2026-05-06T17%3A55%3A12Z&sks=b&skv=2026-02-06&sv=2026-02-06&se=2026-05-06T17%3A55%3A12Z&sr=b&sp=rl&sig=WDk43anDcOKs1V5NXcg8TkCMNLWtCuF%2BFVKru%2FkHkm4%3D
https://github.com/dotnet/sdk/pull/54031/checks?check_run_id=74597582846
even without any changes to tests, such as in the branding PR for 9.0.3xx :
#54191
The team was pinged here #54078 but did not fix the issue. It is blocking PRs and it is not able to be a known issue because it fails in helix in a way which does not get propagated.
it should be disabled in:
main
release/10.0.1xx
release/10.0.3xx
release/9.0.3xx
release/9.0.1xx
For the @dotnet/dotnet-testing-admin team, please investigate this logic at your convenience.
Microsoft.DotNet.Cli.Test.Tests.GivenDotnetTestBuildsAndRunsTestFromCsproj.PathEndsWithSlashOrBackslashexhibits consistent failure in many branches:https://helixr1107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-sdk-refs-pull-54031-merge-40db291649ad4a27ad/dotnet.Tests.dll.9/1/console.3fe54d0c.log?helixlogtype=result&skoid=8eda00af-b5ec-4be9-b69b-0919a2338892&sktid=72f988bf-86f1-41af-91ab-2d7cd011db47&skt=2026-05-06T16%3A55%3A12Z&ske=2026-05-06T17%3A55%3A12Z&sks=b&skv=2026-02-06&sv=2026-02-06&se=2026-05-06T17%3A55%3A12Z&sr=b&sp=rl&sig=WDk43anDcOKs1V5NXcg8TkCMNLWtCuF%2BFVKru%2FkHkm4%3D
https://github.com/dotnet/sdk/pull/54031/checks?check_run_id=74597582846
even without any changes to tests, such as in the branding PR for 9.0.3xx :
#54191
The team was pinged here #54078 but did not fix the issue. It is blocking PRs and it is not able to be a known issue because it fails in helix in a way which does not get propagated.
it should be disabled in:
main
release/10.0.1xx
release/10.0.3xx
release/9.0.3xx
release/9.0.1xx
For the @dotnet/dotnet-testing-admin team, please investigate this logic at your convenience.