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
{{ message }}
Repository navigation
hot_mode_dev_cycle_macos_target__benchmark fails on ARM M1 mac #85654
hot_mode_dev_cycle_macos_target__benchmark is still failing on arm Macs flutter-devicelab-mac-4 and flutter-devicelab-mac-5, though it's passing locally for me.
There's still something off about that CI environment?
Since I couldn't reproduce on my machine, maybe it's something with the Xcode certs?
Is there any way I can get a sudo sysdiagnose -Q (the -Q is optional, but so it doesn't take so long to run)? I'm looking for logging related to the sandbox or security.
Did you take that sysdiagnose while ssh'd in, or did you log in through the GUI to do it?
I collected them from a VNC session. Do you want me to collect another one over an ssh session?
I collected them from a VNC session. Do you want me to collect another one over an ssh session?
Yes, that would be more accurate. I suspect the lack of windowserver is the problem.
If the user is logged in vnc, and then you start an ssh session with the same user, do the tests pass?
@jmagman seems like we need new entitlements for the application to be able to run over ssh:
The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10826 "kLSNoLaunchPermissionErr: User doesn't have permission to launch the app (managed networks)" UserInfo={_LSFunction=_LSLaunchWithRunningboard, _LSLine=2436, NSUnderlyingError=0x115f1e630 {Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x115f1d270 {Error Domain=OSLaunchdErrorDomain Code=125 "Domain does not support specified action" UserInfo={NSLocalizedFailureReason=Domain does not support specified action}}}}}
That's not being hit for this test, I'll fix that for #90892 separately.
I'm not sure what the right incantation is needed to get this working with the sandbox. Let's just remove it for now #92065, having some testing in place is better than it being perfect.
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
jmagman commentedon Jun 30, 2021
@keyonghan are there any
Runner*.crashfiles in ~/Library/Logs/DiagnosticReports for that user with a timestamp matching up to a failing test?jmagman commentedon Jun 30, 2021
Or
flutter_gallery*.crashorFlutter Gallery*.crashfileskeyonghan commentedon Jun 30, 2021
These are the crash list in mac5, but no mentioned ones:
mac5_crash.txt
godofredoc commentedon Sep 16, 2021
@jmagman any other logs that we can collect to help find the root cause?
jmagman commentedon Sep 17, 2021
Since I couldn't reproduce on my machine, maybe it's something with the Xcode certs?
Is there any way I can get a
sudo sysdiagnose -Q(the-Qis optional, but so it doesn't take so long to run)? I'm looking for logging related to the sandbox or security.godofredoc commentedon Oct 14, 2021
@jmagman generated the system diagnose and shared from drive. This is the link: https://drive.google.com/file/d/1Woc7iW7dmkuCQoLv6482HhyBh8OdSgRr/view?usp=sharing
jmagman commentedon Oct 14, 2021
Thanks @godofredoc.
Crashing with an ad-hoc codesign failure:
Logs show the build settings:
But it's not using
S8QB4VV633, it's signing ad-hoc (no cert):I don't think this is related to it being an M1 machine, it's some cert/keychain/some other code signing issue.
7 remaining items
godofredoc commentedon Oct 15, 2021
jmagman commentedon Oct 15, 2021
Yes, that would be more accurate. I suspect the lack of windowserver is the problem.
If the user is logged in vnc, and then you start an ssh session with the same user, do the tests pass?
godofredoc commentedon Oct 15, 2021
I did the following:
godofredoc commentedon Oct 15, 2021
By the way if you want to run some experimentation you can run the following in mac-4:
godofredoc commentedon Oct 18, 2021
@jmagman seems like we need new entitlements for the application to be able to run over ssh:
jmagman commentedon Oct 18, 2021
I just tried this
sshd into the machine and the test passed?godofredoc commentedon Oct 18, 2021
It fails consistently for me when running from the ssh terminal. Did you by any chance run it from a terminal inside the vnc session?
jmagman commentedon Oct 19, 2021
I used Secure Shell and ssh'd into the bridge and then mac-4.
godofredoc commentedon Oct 19, 2021
Do we also need to remove the defaults from
flutter/dev/devicelab/lib/framework/ios.dart
Line 146 in be8d29f
I removed the ios_signing dependency but the tests are still failing:
jmagman commentedon Oct 19, 2021
That's not being hit for this test, I'll fix that for #90892 separately.
I'm not sure what the right incantation is needed to get this working with the sandbox. Let's just remove it for now #92065, having some testing in place is better than it being perfect.
godofredoc commentedon Oct 20, 2021
This is now passing consistently on Mac M1s.
jmagman commentedon Oct 20, 2021
Thanks @godofredoc!
github-actions commentedon Nov 3, 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.