This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Update CoreFX CI packages to NetcoreApp3 #18760
Merged
Conversation
This file contains hidden or 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
A-And
changed the title
Merged
|
@dotnet-bot test this please |
|
A substantial amount of failures were fixed because of this change. |
|
Yes, it looks a lot better. |
jkotas
approved these changes
Jul 3, 2018
picenka21
pushed a commit
to picenka21/runtime
that referenced
this pull request
Feb 18, 2022
* Update to FX CI packages to NetcoreApp3 * Add Extra Dependencies * Enable all tests fixed by change Commit migrated from dotnet/coreclr@f32c75e
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.
Updates restored packages.
@jkotas mentioned some failures we're seeing are due to CoreFX mismatch - setting
TargetFrameworkbefore specifying dependencies restorednetstandardversions of libraries. MovingTargetFrameworkup seems to have fixed the issue.