-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Disable most of S.T.Json trimming tests on AOT the right way #101418
Conversation
These don't seem to use the source generator, so they're not really "trimming tests" and obviously they don't work. The underlying issue to fix them up has been closed.
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
@@ -1,7 +1,9 @@ | |||
<Project DefaultTargets="Build"> | |||
<Import Project="$([MSBuild]::GetPathOfFileAbove(Directory.Build.props))" /> | |||
|
|||
<ItemGroup> | |||
<!-- These tests need to be rewritten to use source generator: https://github.com/dotnet/runtime/issues/53437, |
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.
This issue is closed. Can we either reopen it or open a new one?
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.
Reopened #53437 but per my experience, something in Future milestone is usually as good as closed
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.
Agreed. But it is bad to link a tracking comment to a closed issue. If we aren't going to fix the issue, we should remove/reword the comment.
…101418) These don't seem to use the source generator, so they're not really "trimming tests" and obviously they don't work.
…101418) These don't seem to use the source generator, so they're not really "trimming tests" and obviously they don't work.
These don't seem to use the source generator, so they're not really "trimming tests" and obviously they don't work. The underlying issue to fix them up has been closed.