Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wasm] Fix perf pipeline builds #72234

Merged
merged 1 commit into from
Jul 15, 2022
Merged

Conversation

radical
Copy link
Member

@radical radical commented Jul 15, 2022

Perf pipeline builds broke recently as detailed in #72104, and #72105 . AOT builds broke because il-linking would result in 10 assemblies, instead of 145! This was because the default is TrimMode=full now.

Note: This restores the old behavior. But we want to eventually enable TrimMode=full.

Fixes #72104
Fixes #72105

@radical radical added arch-wasm WebAssembly architecture area-Build-mono labels Jul 15, 2022
@radical
Copy link
Member Author

radical commented Jul 15, 2022

/azp run runtime-wasm

@ghost ghost assigned radical Jul 15, 2022
@ghost
Copy link

ghost commented Jul 15, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Perf pipeline builds broke recently as detailed in #72104, and #72105 . AOT builds broke because il-linking would result in 10 assemblies, instead of 145! This was because the default is TrimMode=full now.

Fixes #72104, and #72105 .

Author: radical
Assignees: -
Labels:

arch-wasm, area-Build-mono

Milestone: -

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical radical force-pushed the fix-perf-pipeline branch from c7cfad0 to c6a97fa Compare July 15, 2022 00:23
@radical
Copy link
Member Author

radical commented Jul 15, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lewing
Copy link
Member

lewing commented Jul 15, 2022

I don't think we should make partial the default, the only thing breaking in this case is the perf pipeline and making more aggressive trimming is the right default for wasm outside of blazor

@radical
Copy link
Member Author

radical commented Jul 15, 2022

I don't think we should make partial the default, the only thing breaking in this case is the perf pipeline and making more aggressive trimming is the right default for wasm outside of blazor

I'm testing TrimMode=full in #72244 . And this PR will unblock the perf pipeline.

Copy link
Member

@lewing lewing left a comment

Choose a reason for hiding this comment

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

I'll approve this to unblock the perf lane immediately but we need to resolve the new modes properly

@radical radical merged commit e5a47d6 into dotnet:main Jul 15, 2022
@radical radical deleted the fix-perf-pipeline branch July 15, 2022 04:56
@ghost ghost locked as resolved and limited conversation to collaborators Aug 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Build-mono
Projects
None yet
2 participants