Skip to content

Conversation

@eerhardt
Copy link
Member

Now that we have a new SDK with the latest linker settings, we need to change how we invoke the linker during the trimming tests.

See #39126 and #39158 which came in hours apart. Fixing the conflict that occurred between them.

Now that we have a new SDK with the latest linker settings, we need to change how we invoke the linker during the trimming tests.
@ghost
Copy link

ghost commented Jul 14, 2020

Tagging subscribers to this area: @safern, @ViktorHofer
Notify danmosemsft if you want to be subscribed.

@eerhardt
Copy link
Member Author

The linker-tests are passing, which this change only affects them. The test failure for Threading.Tasks.Parallel is unrelated.

@eerhardt eerhardt merged commit 345ab77 into dotnet:master Jul 15, 2020
@eerhardt eerhardt deleted the FixLinkerTests branch July 15, 2020 17:08
Copy link
Member

@joperezr joperezr left a comment

Choose a reason for hiding this comment

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

LGTM. I believe that means we now are not really waiting for any new updates in terms of SDK right as we have merged the other changes on the properties or am I missing something?

@eerhardt
Copy link
Member Author

The other linker properties got fixed with #39158 - when the new SDK came into the branch.

I believe that means we now are not really waiting for any new updates in terms of SDK

As far as I know, we should be hooked up with all the latest linker and SDK changes. With this change, I made a deliberate failure in my linking test, ran it and saw the failure locally. So I think we are running the linker correctly now.

@karelz karelz added this to the 5.0.0 milestone Aug 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
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.

5 participants