-
Notifications
You must be signed in to change notification settings - Fork 206
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
[NativeAOT-LLVM] Build target and host packages for WASM on the same platform #2133
[NativeAOT-LLVM] Build target and host packages for WASM on the same platform #2133
Conversation
This matches how the build for other artifacts is set up. We must take care to disable building the corresponding "host" platform, otherwise the publishing process will be racy (since both builds will end up producing "host" packages of the same name).
Packages produced in the test run looked reasonable. |
This reverts commit db3c8e4.
- ${{ else }}: | ||
- script: $(Build.SourcesDirectory)/src/tests/build$(scriptExt) nativeaot $(buildConfigUpper) ${{ parameters.archType }} ${{ parameters.testFilter }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Miscellaneous YAML cleanup.
@dotnet/nativeaot-llvm |
This looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you!
The `''` in `'tree nativeaot'` are significant.
Part of the change unintentionally made the CI run all of the Pri0 runtime tests. I have reverted that. |
Was the loss of the WIndows x64 Release build an intentional effect of this PR? |
Yes, it was. What used to be built "on" the windows_x64 platform is now built "on" browser_wasm_win. Otherwise we would be in a situation where the win-x64 package would be produced twice (and only one of them would have the right content). |
This matches how the build for other artifacts is set up.
We must take care to disable building the corresponding "host" platform, otherwise the publishing process will be racy (since both builds will end up producing "host" packages of the same name).
Hopefully, this is the last fix needed for package publishing to work.