-
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
[8.0] Failing to build native components #94823
Comments
Tagging subscribers to this area: @hoyosjs Issue DetailsError Blob{
"ErrorMessage": "",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": true
} Reproduction StepsThe release/8.0 branch is currently hitting this build error in multiple PRs like this arcade codeflow: #94792 I see at least 3 different error messages. dotnet-linker
|
Author: | carlossanlop |
---|---|
Assignees: | - |
Labels: |
|
Milestone: | 8.0.x |
This was worked around by bumping to the windows.vs2022preview.amd64 build image. |
Anyone found how can I compile coreclr without hitting this error? or do i revert back to a commit for now? |
@khushal1996 make sure you use latest Visual Studio. |
Thanks. It worked. |
Seems we are hitting this in 7.0 too. Example: #96778 |
The error message (
from https://dev.azure.com/dnceng-public/public/_build/results?buildId=568770&view=logs&jobId=8bc6aff5-1400-5bca-e671-ee99bfbeafc5&j=8bc6aff5-1400-5bca-e671-ee99bfbeafc5&t=81713026-4c8d-5b63-02ce-dd6e5e4b94da. Is this issue still active or could we close it? |
I agree that this error message pattern is way too broad since it'd match any native build error. |
The release/8.0 branch is currently hitting this build error in multiple PRs like this arcade codeflow: #94792
I see at least 3 different error messages.
dotnet-linker
windows-x64 release Runtime_Release
runtime
CoreCLR Product Build windows x64 checked
runtime
windows-arm64 Release NativeAOT_Libraries
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=471724
Error message validated:
ninja: build stopped: subcommand failed.
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/16/2023 2:08:57 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: