-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[7.0] Installer build failure: HostActivation Tests in coreclr windows_x86 & coreclr Linux_musl_x64 #86518
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsError BlobImportant: There is a similar issue open specifically for 6.0, but please confirm they have the same root cause before marking this one as duplicate of the other one. {
"ErrorMessage": "",
"BuildRetry": false,
"ErrorPattern": "HostActivation\.Tests_net7\.0_x(64|86).html \[net7\.0\|x(64|86)\]",
"ExcludeConsoleLog": true
} Reproduction StepsBoth failures found in the same 7.0 PR: #86453 x64:
x86:
|
These look like versioning problems somewhere in the host tests, an example of the failure:
Weird. Is this a one-time thing, or does it happen more frequently? /fyi @elinor-fung |
This is not just the host tests. Runtime test failure due to a similar mismatch:
The release/7.0-staging has Lines 4 to 8 in a12825a
|
#86297 updated the |
Ah, that's my fault. I should've bumped both numbers together like in previous months (example https://github.com/dotnet/runtime/pull/84316/files). Sending a PR right now. |
Closing, should be fixed now. |
Error Blob
Important: There is a similar issue open specifically for 6.0, but please confirm they have the same root cause before marking this one as duplicate of the other one.
Reproduction Steps
Both failures found in the same 7.0 PR: #86453
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=279134&view=results
x64:
Installer Build and Test coreclr Linux_musl_x64 Release
Build
x86:
Installer Build and Test coreclr windows_x86 Debug
Build
Known Issue Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: