Skip to content

Conversation

@yusuf-goog
Copy link
Contributor

@yusuf-goog yusuf-goog commented Feb 9, 2022

Update Xcode version to 13a233 for mac builders.

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.

List which issues are fixed by this PR. You must list at least one issue.

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Update Xcode version to 13a233 for mac builders.
@yusuf-goog
Copy link
Contributor Author

For #94078

device_type: none
mac_model: Macmini8,1
xcode: 12c33
xcode: 13a233
Copy link
Contributor

Choose a reason for hiding this comment

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

OS will also need to get changed to 12.0.1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed, set to 12.2, which is the new version deployed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Per @jmagman I changed all the mac builders to be at Mac-12, rather then pegged at a more specific version.

Copy link
Contributor

@godofredoc godofredoc left a comment

Choose a reason for hiding this comment

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

LGTM but let's wait for the ongoing release to get completed.

@jmagman
Copy link
Member

jmagman commented Feb 9, 2022

Why did https://ci.chromium.org/p/flutter/builders/try/Mac%20build_aar_module_test/13799 run on a Mac-10.15.7 machine? https://chromium-swarm.appspot.com/bot?id=build887-m9
I was expecting the Mac tests to instead fail because there were no available staging machines that matched the requested OS.

@godofredoc
Copy link
Contributor

Why did https://ci.chromium.org/p/flutter/builders/try/Mac%20build_aar_module_test/13799 run on a Mac-10.15.7 machine? https://chromium-swarm.appspot.com/bot?id=build887-m9 I was expecting the Mac tests to instead fail because there were no available staging machines that matched the requested OS.

That's a devicelab test that we run on presubmit, .ci.yaml also needs an update for this test.

@CaseyHillers
Copy link
Contributor

FYI tests are failing on:

xcodebuild: error: unable execute utility "/opt/s/w/ir/cache/osx_sdk/XCode.app/Contents/Developer/usr/bin/xcodebuild" because it requires a newer version of macOS.

@yusuf-goog
Copy link
Contributor Author

Is there a good reason to peg it to specifically Mac-12.2? Should we set it to Mac-12?

@jmagman
Copy link
Member

jmagman commented Feb 9, 2022

Is there a good reason to peg it to specifically Mac-12.2? Should we set it to Mac-12?

I don't have a preference, this mac_ios combination is working:

flutter/.ci.yaml

Lines 109 to 111 in 0ce527e

os: Mac-12.0
device_os: iOS-15.1
xcode: 13a233

@yusuf-goog yusuf-goog requested a review from zanderso February 10, 2022 02:07
@jmagman
Copy link
Member

jmagman commented Feb 10, 2022

Why did https://ci.chromium.org/p/flutter/builders/try/Mac%20build_aar_module_test/13799 run on a Mac-10.15.7 machine? https://chromium-swarm.appspot.com/bot?id=build887-m9 I was expecting the Mac tests to instead fail because there were no available staging machines that matched the requested OS.

That's a devicelab test that we run on presubmit, .ci.yaml also needs an update for this test.

Does that mean it will work post-merge once .ci.yaml config changes land? This failure, for example, isn't in the devicelab: https://ci.chromium.org/p/flutter/builders/try/Mac%20build_tests_2_4/15803

@godofredoc
Copy link
Contributor

Why did https://ci.chromium.org/p/flutter/builders/try/Mac%20build_aar_module_test/13799 run on a Mac-10.15.7 machine? https://chromium-swarm.appspot.com/bot?id=build887-m9 I was expecting the Mac tests to instead fail because there were no available staging machines that matched the requested OS.

That's a devicelab test that we run on presubmit, .ci.yaml also needs an update for this test.

Does that mean it will work post-merge once .ci.yaml config changes land? This failure, for example, isn't in the devicelab: https://ci.chromium.org/p/flutter/builders/try/Mac%20build_tests_2_4/15803

Mac_build tests are hostonly tests, they use different .ci.yaml configurations from devicelab tests. All the tests need to pass on presubmit and as long as we keep half of the capacity running on 10.15 we should not break postsubmit tests as after landing the PR, postsubmit tests will still use the old configs for ~45mins until they are propagated. Once the configs are fully propagated it will be safe to upgrade the remaining machines.

@keyonghan
Copy link
Contributor

New version of cocoon has been deploy with flutter/cocoon#1597.
Manually triggered all the tests, and 12.2 is being picked up.

@jmagman
Copy link
Member

jmagman commented Feb 10, 2022

#98210 override should also be reverted on this change.

@jmagman
Copy link
Member

jmagman commented Feb 10, 2022

#98210 override should also be reverted on this change.

Though I can to it in a follow-up.

@goderbauer goderbauer added c: contributor-productivity Team-specific productivity, code health, technical debt. team-infra Owned by Infrastructure team labels Feb 10, 2022
@flutter-dashboard
Copy link

Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change).

If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

Changes reported for pull request #98144 at sha fb87c3b

@flutter-dashboard flutter-dashboard bot added the will affect goldens Changes to golden files label Feb 10, 2022
@fluttergithubbot fluttergithubbot deleted the yusuf-goog-patch-1 branch February 11, 2022 09:05
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Feb 11, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 11, 2022
zanderso added a commit that referenced this pull request Feb 11, 2022
@zanderso
Copy link
Member

It looks like this is breaking the Mac web_tool_tests on the framework tree. Revert is here #98263.

zanderso added a commit that referenced this pull request Feb 11, 2022
jmagman pushed a commit to jmagman/flutter that referenced this pull request Feb 11, 2022
@jmagman jmagman mentioned this pull request Feb 11, 2022
8 tasks
clocksmith pushed a commit to clocksmith/flutter that referenced this pull request Mar 8, 2022
clocksmith pushed a commit to clocksmith/flutter that referenced this pull request Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. team-infra Owned by Infrastructure team will affect goldens Changes to golden files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants