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

[release/3.1] Fix use of ilasm during test builds when using a 3.0 SDK #27818

Merged
merged 2 commits into from
Nov 11, 2019

Conversation

hoyosjs
Copy link
Member

@hoyosjs hoyosjs commented Nov 11, 2019

The restore logic in buildtools tried to use a netcoreapp2.1 TFM for Linux-musl.
This ended up restoring Linux-x64 binaries which then broke the test build.
This change works around this by saving a copy of the depproj that BuildTools used into
the tree and restore it as a 3.0 app manually in init-tools on our side of the build.

The restore logic in buildtools tried to use a netcoreapp2.1 TFM for Linux-musl.
This ended up restoring Linux-x64 binaries which then broke the test build.
This change works around this by saving a copy of the depproj that BuildTools used into
the tree and restore it as a 3.0 app manually in init-tools on our side of the build.
@hoyosjs hoyosjs requested a review from jashook November 11, 2019 20:27
@hoyosjs
Copy link
Member Author

hoyosjs commented Nov 11, 2019

cc: @dotnet/coreclr-infra

@hoyosjs
Copy link
Member Author

hoyosjs commented Nov 11, 2019

In the test build, ilasm got correctly restored for musl, and ran properly.

@sergiy-k
Copy link

Approved for 3.1 to unblock infrastructure.

@hoyosjs hoyosjs merged commit fd44c0f into dotnet:release/3.1 Nov 11, 2019
@hoyosjs hoyosjs deleted the juhoyosa/fix-ilasm branch November 11, 2019 23:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants