-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 tests failing in CI #75429
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsHit in #75408. Full log: https://dev.azure.com/dnceng-public/public/_build/results?buildId=11824&view=ms.vss-test-web.build-test-results-tab&runId=235664&resultId=100162&paneView=debug
|
Failed again in #75407
|
I looked at the logs of both of those failures and it's weird. The test log says something like (simplified): Command failed with exit code 1: /root/runtime/.dotnet/dotnet publish ...
Standard output:
... MSBuild startup and so on ...
StartupHookWithMultipleIncorrectSignatures -> /root/runtime/artifacts/tests/Release/ha/k0ufkmfh.z0w/StartupHookWithMultipleIncorrectSignatures/bin/ There's no stderr printed out. The two failures are on a different test assets but otherwise look very similar. Looking into the logs, the msbuild binlog for the publish command says that the command succeeded in both case. So it's happening for different test assets, on different targets (one is linux_x64, the other one is linux_x64_musl) and rarely. @elinor-fung as FYI and for possible ideas. |
Seems like this is only happening in release/7.0 right now? The tests run the SDK used by the repo to publish test projects/assets. Potential difference I see is that release/7.0 is using RC1 Lines 7 to 8 in cd483c1
while main is using Preview 7 Lines 7 to 8 in 467fef4
Maybe this is actually exposing a bug in RC1? As @vitek-karas pointed out, it looks like the publish succeeds - or at least does not log any errors. But the exit code is 1. This is the binlog for the project in #75429 (comment) (renamed extension): PublishProject.binlog.log. |
This looks basically identical to #74328 |
Closing this as dupe of #74328 since it has the exact same behavior. |
#74328 is not being hit by the CI anymore.
|
The following release/7.0 backport PR hit the 3 symlink failures: #77501 Put_app_directory_behind_symlink
and Put_dotnet_behind_symlink
and Put_satellite_assembly_behind_symlink
|
#77524 added a workaround to main (same as what we did for the wasm failures). I just triggered a backport. |
This was addressed when the repo switched to .NET 7 GA. The workarounds were removed in #79035 |
Hit in #75408. Full log: https://dev.azure.com/dnceng-public/public/_build/results?buildId=11824&view=ms.vss-test-web.build-test-results-tab&runId=235664&resultId=100162&paneView=debug
Report
Summary
The text was updated successfully, but these errors were encountered: