-
Notifications
You must be signed in to change notification settings - Fork 446
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
Rebootstrap SB SDK/artifacts #18763
Rebootstrap SB SDK/artifacts #18763
Conversation
Dealing with some incoherency issues here, I think. First commit:
Second commit (using the output from an earlier VMR build):
|
The failures in the unified-build pipeline are caused by #18768 |
/azp run installer-source-build |
Azure Pipelines successfully started running 1 pipeline(s). |
/backport to release/9.0.1xx-preview2 |
Started backporting to release/9.0.1xx-preview2: https://github.com/dotnet/installer/actions/runs/8067367487 |
@KevinRansom - Can you take a look at these F# failures that are occurring in the VMR build (specifically the installer-source-build pipeline)? The changes that are being made here are to update the SDK version that is used by the build. That's running into a bunch of these
Do your recent changes in dotnet/fsharp#15484 potentially resolve this? Those changes haven't flowed into installer yet. Or otherwise, do you know what should be done to fix this? |
The unified-build pipeline is running into the same error as dotnet/sdk#39050 (comment) which was fixed there. Merging in latest to get that fix. |
Errors in aspnetcore for installer-source-build:
Pretty sure this is because the Roslyn version is the same between the preview.2 source built artifacts being used to bootstrap with and the version of Roslyn that's currently being built in the VMR. It causes non-determinism on which package gets used by source build. Waiting on #18875 to be merged which will upgrade the Roslyn version so that it won't conflict. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't the Arcade Sdk entry in global.json need to be updated as well?
Getting a whole bunch of test failures when attempting to run
This method was newly added in NuGet/NuGet.Client#5645. |
This is necessary in order to get a new SDK with a fixed version of the crossgen2 tool for resolving dotnet/source-build#4007