-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Remove unused suppressions for System.Linq.Expressions #89524
Remove unused suppressions for System.Linq.Expressions #89524
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue Detailsfixes #89206
|
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.
Approving to unblock.
Two questions for my own education:
- What specific change in PR https://github.com/dotnet/runtime/pull/88723/files caused the suppresion errors to start showing up and why?
- Why didn't the CI in that PR show the errors? https://github.com/dotnet/runtime/pull/88723/checks?check_run_id=15146702721
The error only shows up when using the 8.0 Preview 7 SDK to build. This repo isn't using that. |
Correct, we cannot use the Preview7 SDK yet because it is not done. We cannot use the nightly build of APICompat because it depends on preview7 API that was added to runtime. So we're in a situation for a few weeks where we'll not have protection for these. @mthalman another option here would be to just disable the consistency check until we can turn it on in dotnet/runtime. To do that you can set |
Regarding:
Before the change, we were building/shipping
I had the same question, so thanks @mthalman @ericstj for the clarification in your comments. If I understand correctly, I should have had built the runtime with |
You could have, but I honestly wouldn't expect you to realize that. Once we can update to the Preview7 SDK it will be obvious, and hopefully the steps you need to take will be apparent in the error message. Also - you don't need to do it for the whole repo - you could simply do this when building a single src csproj. |
fixes #89206