Use OperatingSystem APIs instead of RuntimeInformation in more places #52548
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsThese are recommended instead of the older APIs.
|
9b9a8eb to
8780dbd
Compare
|
Changing labels as this isn't infrastructure. |
2778c28 to
d03c90f
Compare
ViktorHofer
reviewed
May 18, 2021
src/installer/tests/HostActivation.Tests/MultilevelSDKLookup.cs
Outdated
Show resolved
Hide resolved
These are recommended instead of the older APIs.
d03c90f to
ee0520a
Compare
ViktorHofer
approved these changes
May 18, 2021
akoeplinger
added a commit
to akoeplinger/runtime
that referenced
this pull request
May 20, 2021
After dotnet#52548 some installer tests that were using `PlatformSpecific(TestPlatforms.Windows)` started failing in the runtime-staging pipeline on Linux, even though they shouldn't have been executing. Turns out this is because with dotnet@81771ef we're adding the `-trait category=failing` on the runtime-staging pipeline. This doesn't work since `PlatformSpecific` attribute works by setting the "failing" category. To fix this use a separate trait that can be used to only run the specific tests we want in runtime-staging.
akoeplinger
added a commit
that referenced
this pull request
May 20, 2021
* Fix installer tests on runtime-staging After #52548 some installer tests that were using `PlatformSpecific(TestPlatforms.Windows)` started failing in the runtime-staging pipeline on Linux, even though they shouldn't have been executing. Turns out this is because with 81771ef we're adding the `-trait category=failing` on the runtime-staging pipeline. This doesn't work since `PlatformSpecific` attribute works by setting the "failing" category. To fix this use a separate trait that can be used to only run the specific tests we want in runtime-staging. * Fix: Trait only works on class
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
These are recommended instead of the older APIs.