Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Conversation

@jkoritzinsky
Copy link
Member

Currently, the core-setup scripting to use a local CoreCLR build depends on the CoreCLR packages. With dotnet/coreclr#27841, we will be able to determine what files are part of the shared framework based on if they are in the sharedFramework folder.

This PR updates the CoreCLR override mechanism to use the sharedFramework folder instead of comparing files against the packages.

Copy link
Member

@dagood dagood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly style comments, but one about this maybe breaking arm64 building on arm64.

@dagood
Copy link
Member

dagood commented Nov 12, 2019

Test failure may be this known flakiness: https://github.com/dotnet/core-setup/issues/8643

Copy link
Member

@dagood dagood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@jkoritzinsky
Copy link
Member Author

Failure is due to a lost connection in AzDO. Rerunning.

@jkoritzinsky jkoritzinsky merged commit 9af1be8 into dotnet:master Nov 13, 2019
@jkoritzinsky jkoritzinsky deleted the coreclr-override-sharedframeworkfolder branch November 13, 2019 01:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants