You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@godofredoc I'm about to merge a fix for the last test failure with #85087. I think getting an M1 set up in CI will be the last thing blocking iOS arm64 simulator work #85059.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
godofredoc commentedon Mar 31, 2021
\cc @jmagman @xster
godofredoc commentedon Apr 1, 2021
flutter-devicelab-mac-4 is ready but it seems to be failing tasks:
jmagman commentedon Apr 1, 2021
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8851131712845907728/+/steps/run_flutter_gallery_ios__start_up/0/stdout
These might need Rosetta installed. Can you add
softwareupdate --install-rosettato the setup?jmagman commentedon Apr 1, 2021
@godofredoc says "rosetta is installed as part of the provisioning. idevice requires the emulation"
Can we confirm whatever
xcrunis on thePATHcontainsarm64e?(note the
arm64eat the end).godofredoc commentedon Apr 1, 2021
This is from the one included in the bundle:
godofredoc commentedon Apr 1, 2021
It was that removing
/opt/flutter/xcode/12c33/XCode.app/Contents/Developer/usr/bin/xcrunand re-running:https://luci-milo.appspot.com/p/flutter/builders/prod/Mac_ios_staging%20flutter_gallery_ios__start_up/135?
jmagman commentedon Apr 1, 2021
So is the next step a recipe change, or is there more for me to investigate, @godofredoc?
godofredoc commentedon Apr 1, 2021
Thanks for helping us identify the issue the next step is to create a new xcode bundle that does not include xcrun. I'll reassign the bug back to me.
godofredoc commentedon Apr 1, 2021
Uploading a new xcode bundle to remove xcrun.
godofredoc commentedon Apr 2, 2021
@jmagman we still have a couple of failures:
jmagman commentedon May 12, 2021
I was able to reproduce
ios_app_with_extensions_testlocally, investigating that now.hot_mode_dev_cycle_macos_target__benchmarkpassed on my machine. @godofredoc Is there a user logged in when that test runs?jmagman commentedon May 13, 2021
I'm tracking the
ios_app_with_extensions_testtest failure in #82402jmagman commentedon Jun 23, 2021
@godofredoc I'm about to merge a fix for the last test failure with #85087. I think getting an M1 set up in CI will be the last thing blocking iOS arm64 simulator work #85059.
jmagman commentedon Jun 23, 2021
#85087 merged, though I can't see if the tests now pass because mac-4 is quarantined for lack of disk space #82492.
jmagman commentedon Jun 30, 2021
Filed #85654 to track down the
hot_mode_dev_cycle_macos_target__benchmarkfailure.godofredoc commentedon Jul 29, 2021
@jmagman @keyonghan I believe we can close this issue, am I right? I see tests running on the Mac M1 machines.
jmagman commentedon Jul 29, 2021
I think so. Once I track down #85654 I'll file an issue to move the machines to the prod pool. Is that right, @godofredoc?
godofredoc commentedon Jul 29, 2021
Sounds good, thanks Jenn.
github-actions commentedon Aug 12, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.