Remove or move some expensive low-value testing #65453
Conversation
When PGO was added, I added it in PR as well just to help with monitoring At this point it's very stable and expensive to run, so we should probably move it out.
Single-file is still tested in our unit tests, but these runs were mainly to test the compatibility of APIs with single-file. We've found that the analyzer does a pretty good job of verifying that without testing, and we still have verification via NativeAOT, which I think is a superset of the testing as a whole.
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsThere are two sets of runs we do right now that aren't very valuable. Single-file is mainly testing API compatiblity and the analyzer has mostly solved that. NativeAOT also now verifies this. PGO is still important, but very stable and only needs to run in the official runs during publishing.
|
carlossanlop
added
area-Infrastructure
and removed
area-Infrastructure-libraries
labels
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThere are two sets of runs we do right now that aren't very valuable. Single-file is mainly testing API compatiblity and the analyzer has mostly solved that. NativeAOT also now verifies this. PGO is still important, but very stable and only needs to run in the official runs during publishing.
|
|
LGTM |
ghost
locked as resolved and limited conversation to collaborators
There are two sets of runs we do right now that aren't very valuable.
Single-file is mainly testing API compatiblity and the analyzer has mostly solved that. NativeAOT also now verifies this.
PGO is still important, but very stable and only needs to run in the official runs during publishing.