NativeAOT: Update NativeAOT integration tests to run with 9.0.1xx-preview1 #20268
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.
Description
There were two issues around NativeAOT integration tests:
TreatWarningsAsErrors=true
With .NET9-p1 NativeAOT integration tests started failing due to dotnet/runtime#96567
This change enabled ILC (NativeAOT compiler) to take
TreatWarningsAsErrors
into account during compilation.Since this flag is set to
true
in integration testing, it caused CI failures.As we are in the process of reducing the number of warnings to 0, until we reach that point we need to run these tests by escaping
TreatWarningsAsErrors=true
setting. This can be achieved by settingIlcTreatWarningsAsErrors=false
.<Module>..cctor(): Using member 'System.Enum.GetValues(Type)'
warningThis PR fixes both of these issues.
/cc: @simonrozsival