Repository navigation
Add CI builder for windows-arm64. - #38394
Conversation
|
@godofredoc @loic-sharma This is the PR for adding windows-arm64 artifacts. |
|
Integrated change to .ci.yaml and rebased. |
|
auto label is removed for flutter/engine, pr: 38394, due to - Please get at least one approved review if you are already a member or two member reviews if you are not a member before re-applying this label. Reviewers: If you left a comment approving, please use the "approve" review action instead. |
|
auto label is removed for flutter/engine, pr: 38394, due to Validations Fail. |
|
@loic-sharma can you please help us with a second review to be able to land this change? |
|
@godofredoc Once this PR gets merged, will artifacts be available within hours, or later in January? |
This change is safe to land but we need a second review. The artifacts will be generated as soon as this PR is landed and uploaded to a different bucket. After coming from vacation I can help with the engine.py change for you to get access to the archives from within the flutter sdk. |
|
Is the engine.py modification still needed? From what I understood, this will be deprecated in January and replaced by current approach. But maybe I missed something. The final goal is to add support to flutter.bat. |
|
Fix name of archive generated to reflect target architecture. |
|
@godofredoc Is there something to add to get arm_host_engine workflow enabled in github CI for this PR? That would help to ensure everything is working as expected before merging this. |
All packages can be cross compiled from an x64 machine. Unittests are disabled, as they require an arm64 machine.
|
Thanks for your help @loic-sharma I ran a full build to check locally all zips are correct: And I get this list of zip files: I should have check everything manually, sorry. I was expecting CI to do its job for me on this. |
|
From Triage: Please wait for @zanderso s review on this one. |
|
Thanks for your precious help @loic-sharma! |
This reverts commit 5a39a88.
|
@pbo-linaro This change had to be reverted as it broke the My guess is this change caused a mismatch between: And: One hacky solution may be to use the target platform only on Windows hosts when building the web SDK? Or is there a better solution? /cc @godofredoc @eyebrowsoffire |
* 5a39a88 Add CI builder for windows-arm64. (flutter-team-archive/engine#38394) * 264aa03 Revert "Add CI builder for windows-arm64. (#38394)" (flutter-team-archive/engine#38729)
|
Probably adding an if for windows platform is the easiest thing to do. Just a question: What does the whole CI check regarding artifacts? Are we sure it's the only package that was broken? |
|
Created a new PR adding a special case for web-sdk artifacts: #38739 |
…8208) * 5a39a88 Add CI builder for windows-arm64. (flutter-team-archive/engine#38394) * 264aa03 Revert "Add CI builder for windows-arm64. (flutter#38394)" (flutter-team-archive/engine#38729)
This PR adds support for windows-arm64 artifacts, using new infrastructure that will be used from January 2023, and replacing https://flutter.googlesource.com/recipes/.
I checked locally that targets are correctly built and expected zips are there 👍.
All packages can be cross compiled from an x64 machine.
Unittests are disabled, as they require an arm64 machine.
Solves this issue: flutter/flutter#115983
Pre-launch Checklist
///).