-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.DotNet.CoreSetup.Test.HostActivation.StartupHooks.Muxer_activation* tests failed #76681
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsInstaller-coreclr-Linux_musl_x64-Release
This doesn't seem to be a dupe of #74328 even though a similar query is linked there. the build failed with code 1.
|
@danmoseley I must be missing it - can you point out what looks different from #74328? They both seem successful |
I thought "exit code 1 even when the build passes" sounded like an infra bug (Eg in MSBuild?), whereas this is just a test failure (??) |
In this case (and in a lot of the tests under installer/), the test actually runs |
Ah - the title of #74328 is super misleading then. It might as well say "Some installer test(s) failed". Now I am not sure what it is encompassing. |
The root problem is around I added a line at the top of the description to hopefully make it clearer that we are seeing installer test failures as a result. I'm going to close this against #74328. |
Installer-coreclr-Linux_musl_x64-Release
https://dev.azure.com/dnceng-public/public/_build/results?buildId=41475&view=ms.vss-test-web.build-test-results-tab&runId=836728&resultId=100173&paneView=debug
This doesn't seem to be a dupe of #74328 even though a similar query is linked there. the build failed with code 1.
The text was updated successfully, but these errors were encountered: