-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[ci] Run Windows Arm64 build tests post-submit #6166
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
Conversation
99fa0c7
to
044417c
Compare
.ci.yaml
Outdated
@@ -1490,6 +1491,7 @@ targets: | |||
|
|||
- name: Windows_x64 windows-build_all_packages stable | |||
recipe: packages/packages | |||
presubmit: false |
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.
I assume this was supposed to go on line 1510 instead (Win arm64 stable)?
If capacity is low, I would suggest just deleting that one instead. The chances of breaking only the Windows arm64 build of plugins only on stable seems extremely low, so we could halve our Windows arm64 usage for this repo with probably no appreciable impact on coverage.
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.
Good catch, fixed!
The majority of Windows Arm64 capacity is used by Dart's tests, not Flutter's tests. I think keeping the Windows Arm64 stable test is fine unless you'd prefer to remove it.
My understanding is that the infra team would need to significantly increase their number of Windows Arm64 machines to also support the try pool, so for now they're skipping that.
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.
I would probably remove it absent some reason we believe it will catch actual issues that the other bot won't, but I don't feel strongly about it.
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
flutter/packages@48048f6...078c2a3 2024-02-22 [email protected] Manual roll Flutter from 5129806 to efee280 (47 revisions) (flutter/packages#6180) 2024-02-22 [email protected] Manual roll Flutter (stable) from bae5e49 to abb292a (1 revision) (flutter/packages#6179) 2024-02-21 [email protected] [in_app_purchase] Convert refreshReceipt(), startObservingPaymentQueue(), stopObservingPaymentQueue(), registerPaymentQueueDelegate(), removePaymentQueueDelegate(), showPriceConsentIfNeeded() to Pigeon (flutter/packages#6165) 2024-02-21 [email protected] [camerax] Modifies initialized camera info to reflect default AF/AE modes and the ability to set focus points for each (flutter/packages#6109) 2024-02-21 [email protected] [camerax] Implements `setFocusPoint`, `setExposurePoint`, `setExposureOffset` (flutter/packages#6059) 2024-02-21 [email protected] [various] Commit Windows build migrations (flutter/packages#6175) 2024-02-21 [email protected] [flutter_markdown] Support wasm (flutter/packages#6168) 2024-02-21 [email protected] [ci] Run Windows Arm64 build tests post-submit (flutter/packages#6166) 2024-02-21 [email protected] [url_launcher] Remove `renderView` usage (flutter/packages#6137) 2024-02-21 [email protected] [camera_android_camerax] Fix typo in readme (flutter/packages#6143) 2024-02-21 [email protected] [local_auth] Switch iOS endorsement to `local_auth_darwin` (flutter/packages#6107) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
The Flutter try pool does not have any Windows Arm64 machines. Thus, any Windows Arm64 pre-submit tests would fail without
bringup: true
as there's no machines to run them.This change will allow us to promote the Windows Arm64 build tests out of
bringup
.See: flutter/flutter#141986
Part of flutter/flutter#129813
Pre-launch Checklist
dart format
.)[shared_preferences]
pubspec.yaml
with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.md
to add a description of the change, following repository CHANGELOG style.///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.