-
Notifications
You must be signed in to change notification settings - Fork 132
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
Stage 2 Builds failing during runtime build #4355
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
@mthalman would you know by any chance who from runtime we should ping for this issue? I looked through |
cc @ViktorHofer, @ericstj |
That's due to dotnet/sdk@170fa21. @ericstj has a reactionary change ready for runtime. |
I was planning to add those when we ingested APICompat to runtime. Instead I went ahead and made the fixes. I still think source build will be broken because it will insist on the suppressions being up to date / as will runtime. |
@ViktorHofer is adding a patch to disable APICompat in runtime which should resolve the issues temporarily. |
[Triage] We are expecting this to be unblocked by the #4362 that needs to be done in conjunction with with latest sdk flow. |
I think this was fixed since we rebootstrapped and the latest sdk flow went in. Leaving #4362 open since we continue to rebootstrap to get builds green post the installer -> sdk merge. |
Build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2437450&view=logs&j=3121c41d-6088-53a5-4ef6-9a86f3460fe9&t=334539f4-dcef-5cad-a240-02997b3146e7
Error:
The text was updated successfully, but these errors were encountered: