Skip to content

Conversation

@stuartmorgan-g
Copy link
Collaborator

This adds a bringup LUCI version of the macOS-host custom package tests. This is the first attempt to migrate a flutter/packages or flutter/plugins test to macOS ARM, so is experimental.

The motivation for doing this migration now is to see if it can unblock #2816, which doesn't seem to be able to run successfully on Cirrus ARM machines (very possibly due to the same issue that blocked flutter/plugins migrations to ARM on Cirrus).

This adds a bringup LUCI version of the macOS-host custom package tests.
This is the first attempt to migrate a flutter/packages or
flutter/plugins test to macOS ARM, so is experimental.

The motivation for doing this migration now is to see if it can unblock
flutter#2816, which doesn't seem to
be able to run successfully on Cirrus ARM machines (very possibly due
to the same issue that blocked flutter/plugins migrations to ARM on
Cirrus).
@stuartmorgan-g
Copy link
Collaborator Author

(If this doesn't end up working, I'll try a LUCI Intel version of this test instead to see if that unblocks the iOS pigeon PR.)

channel: stable

- name: Mac_arm64 custom_package_tests master
bringup: true # New configuration
Copy link
Member

Choose a reason for hiding this comment

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

Did you try a led run with this? Suspect you'll hit flutter/flutter#113231

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

My led-fu is very weak, but I though the task config already had to exist to point to in a led run. Is that no longer the case?

Copy link
Member

Choose a reason for hiding this comment

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

Technically you can copy an existing config and edit it go/flutter-luci-recipes#testing-a-local-change-for-a-new-builderrecipe. However I've never had the patience to do that.
Usually I remove bringup and presubmit in the PR and let it run in presubmit, and then revert that before merging. ci.yaml validation would fail though. You can normally be sneaky and use an existing test and just say swap out target_file to have it run in presubmit, but you have the added complication of there being no existing Mac_arm64 builders.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, that sounds about like what I've done in the past; this was to bootstrap me to something where I could play around with things in presubmit in a follow-up PR.

But since we have known ARM breakage I'll hold off on this, and maybe explore doing an Intel version instead. Thanks for the pointer to that issue!

Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

Change LGTM though I suspect this may fail due to arm infra issues. Worth a shot though.

@stuartmorgan-g
Copy link
Collaborator Author

Re-opening to try again now that flutter/flutter#113231 is fixed.

@stuartmorgan-g stuartmorgan-g added the autosubmit Merge PR when tree becomes green via auto submit App label Jan 14, 2023
@auto-submit auto-submit bot merged commit 15ffa8a into flutter:main Jan 14, 2023
@stuartmorgan-g stuartmorgan-g deleted the luci-mac-custom-tests branch January 14, 2023 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants