Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Is this caused by a specific test that was disabled recently or do you know why we started hitting this now?
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.
No, this is not a disabled test,
System.Text.Json.SourceGeneration.Roslyn4.4.Testshas always beenIgnoreForCIon mobile, so it never runs on the Apple mobile CoreCLR legs, but it was still published and trimmedWhat actually fails is ILLink crashing during that publish trim with an unhandled
ArgumentOutOfRangeExceptioninMono.Cecil.The crash first appears in the https://dev.azure.com/dnceng-public/public/_build/results?buildId=1515988, which points to #130164 and #130665, each added a
[JsonSerializable(typeof(...))]entry to theTestTypesContextsource-generated context that these tests compile, which could have caused the error.I will create a tracking issue if it doesn't exist.
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.
Tracked in #131122
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.
I'm wondering if this a real issue not just a CI thing which warrant a bigger attention. Could it be something with trimmer that is broken on mobile @vitek-karas ?
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.
It is a latent Cecil bug that only appears once the assembly grows past a certain size. I believe it is worth further investigation and don't think it is mobile-specific.