-
Notifications
You must be signed in to change notification settings - Fork 841
Update SDK to 23523.1 #4606
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
Update SDK to 23523.1 #4606
Conversation
|
@wtgodbe should aspnet-build be a required reviewer in this repo too? |
|
@joperezr how do you normally handle review requests in this repo? I see there's no Codeowners file - I'd be happy to be a required reviewer on the things build-ops does in Extensions (namely SDK updates) |
|
If the build is green - merge it :) |
|
This SDK is bugged: |
|
This failure is the one where multiple tools in a |
|
I re-ran the build and it still fails. Interestingly, dotnet/aspnetcore#51588 successfully passed in the dotnet/aspnetcore repo. @JL03-Yue do you have an update on that fix? Will updating the SDK to a newer version fix this failure? |
|
|
|
I updated this PR to use the same SDK version as ASP.NET Core. There is a new error:
|
|
FYI this overlaps with #4554 that needed updated SDKs for other fixes. We'll take whichever succeeds first. |
|
@dotnet/domestic-cat strange error from the 9.0 sdk here |
|
Why is the runtime version in global.json set to 8, but the SDK/arcade is 9.0? |
|
@joeloff we install both 8 and 9 runtimes for testing. |
We run tests against 8.0, and because we use the SDK for 9.0 we need to have a runtimes section that pulls in 8.0 runtime in order for the tests to run |
|
@dotnet/domestic-cat? |
|
I would guess the SDK update is blocked by dotnet/sdk#36659. |
There's a number of main PRs blocked on the Arcade issue right now because of an incorrect subscription. Once that is fixed, things should improve. Arcade change is merged and I think the subscriptions were fixed too, but this now has to flow through the validation pipeline, etc. and make its way to SDK |
|
@amcasey, we don't even get that far, we're still hitting |
|
@Tratcher I can't tell from the thread - is the |
|
No, the error is not understood and it's not clear how to make progress. |
|
I ran this locally (reconstructed as best I could from the pipeline yaml plus the console logs) and it succeeded Edit: but I don't have powershell 7 - I'll try that |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
d74edd0 to
47da9e1
Compare
Regular BuildOps update
Microsoft Reviewers: Open in CodeFlow