Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[main] Re-Bootstrap Source Build to .NET 10.0.100-preview.2.25155.1 #47290

Closed
wants to merge 1 commit into from
Closed

[main] Re-Bootstrap Source Build to .NET 10.0.100-preview.2.25155.1 #47290

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 5, 2025

Backport of #47289 to main

/cc @ViktorHofer @dotnet-sb-bot

@github-actions github-actions bot requested review from a team as code owners March 5, 2025 15:24
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Mar 5, 2025
@ViktorHofer ViktorHofer mentioned this pull request Mar 5, 2025
Open
@ViktorHofer ViktorHofer self-assigned this Mar 5, 2025
@ViktorHofer
Copy link
Member

ViktorHofer commented Mar 5, 2025 •
edited
Loading

D:\a_work\1\vmr\src\fsharp\artifacts\Bootstrap\fsc\Microsoft.FSharp.Targets(354,9): error MSB6006: "fsc.exe" exited with code 57005. [D:\a_work\1\vmr\src\fsharp\src\FSharp.Core\FSharp.Core.fsproj::TargetFramework=netstandard2.0]

0xDEAD hexadecimal integer 57005. Pointer related? Seems to be deterministic as multiple legs are failing with that error. @jkotas any idea? This happens with the latest P2 built SDK.

@ViktorHofer
Copy link
Member

cc @MichalStrehovsky as well

@ViktorHofer
Copy link
Member

ViktorHofer commented Mar 5, 2025 •
edited
Loading

On Unix (non-source-only) this fails with 134 - SIGABRT

@build-analysis build-analysis bot mentioned this pull request Mar 5, 2025
Open
@MichalStrehovsky
Copy link
Member

cc @MichalStrehovsky as well

That looks like some bad crash of the CoreCLR VM, maybe someone from @mangod9 team can take a look?

@mangod9
Copy link
Member

mangod9 commented Mar 6, 2025

@AndyAyersMS has investigated and has made a fix: dotnet/runtime#113181

@ViktorHofer
Copy link
Member

Closing in favor of #47359 which has the newer SDK with the runtime fix.

@ViktorHofer ViktorHofer closed this Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ViktorHofer ViktorHofer ViktorHofer approved these changes

Assignees

@ViktorHofer ViktorHofer

Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ViktorHofer @MichalStrehovsky @mangod9 @dotnet-sb-bot