-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
iOS simulator unavailable, device type profile not found #97303
Comments
Re-running the test in #97295, I don't see it failing in other PRs (that PR is definitely not the issue though) |
Suspect the re-run will succeed, the simulator list looks correct:
Reducing priority. |
I've seen that
|
And interestingly only the 14.3 iPhone 12* devices are available...?
|
I'll monitor the builds to see if this flake occurs again |
Waiting for the battery healthcheck to land in production. |
I don't think this is related to the tethered device's health, it's that the simulators aren't set up in a way Xcode can find them. |
Would this be fixed with the new way to provide runtimes? |
Seem the failures happened on only two bots: build857-m9 and build866-m9. Take a further look, builder /cc @jmagman Any settings/config that may cause this behavior from bot side? All bots should be configured in the same way though. |
Maybe the simulator device types were removed on those machines? I can't figure out where on disk the different types of simulator device images would live though. |
Could this be related to testing the runtimes functionality of osx_sdk in those two bots? |
Not sure, from #97303 (comment) the symptoms look different, the simulator runtimes (OS version I could change the test to |
@keyonghan can we delete the caches on those two machines and manually re-run the test? |
I think they are in |
Cleaning caches helps! Here is a success run with a pass on build857-m9. Will run a couple of times, and also on the other bot to verify. |
Five times all passed on build857-m9. |
This just happened again: Failing test:
|
The two failed builds happened on https://chromium-swarm.appspot.com/bot?id=build818-m9 and https://chromium-swarm.appspot.com/bot?id=build817-m9, both had an earlier failed run on Trying an led run on a good bot to validate. |
An led run on build819: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/728275e5db28c25ac54938b9e956ab0e40a80813c891077d4d8edf567cc8398b/+/build.proto So far the device type profile is there. Expectation is the build will pass. |
Can we try led runs on build818 and 817 and check the content of the xcode simruntime folder from ssh? |
Latest update: I was blocked on permission issue to ssh to these bots, and @godofredoc is helping validate some cases instead of simply refreshing the caches. From godofredo:
|
What's the status of this? The Engine tree has been closed for 17 hours. |
Out of curiosity, why is Mac Web Engine left on Mac 10? I kicked off a build in https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20Web%20Engine/24081/overview to see if it would pass on Mac 12. |
It's on macOS 10.15 and Xcode 12.3 because Safari won't launch on the Xcode 13 simulators #99885 |
Copying from internal chat (thanks @keyonghan for the recap):
The hesitation here is there's an issue with the recipes not correctly identifying older xcodes/simulators being used, and not wiped the directory. AIs:
|
I went through the engine build dashboard to find Mac 10 bots run that failed with xcode 13. I gathered the list and will start wiping them:
Update: I'm blocked from accessing m9 bots. Requesting permissions for the engprod team to have access (currently @godofredoc is the only one) |
Talked with @yjbanov and it seems like Mac Web Engine is running on Mac 12 now. We landed flutter/engine#32337 as the issue is running this test on the corrupt Mac 10 bots. |
This builder failed many times on Xcode 13 due to #99885 /cc @godofredoc it passed a few times for reasons we couldn't figure out. |
The latest build is hanging. I guess we need a revert: flutter/engine#32340 |
I have some local changes I used for validation yesterday unfortunately I haven't been able to test them yet. I'll upload the current version of the recipe change just in case someone has free cycles to validate it. |
Here is a run with the changes to remove the runtimes properly: https://chromium-swarm.appspot.com/task?id=59f5766358a6e610 |
All bots are cleaned up, and we should be ready to land flutter/engine#32340 to unblock the tree. |
After 15+ green runs, this looks fixed. Thanks Keyong! |
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 |
Try job
module_test_ios
trying to create a simulator:List of simulators shows all the simulators are "unavailable, device type profile not found"
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8823963857735512193/+/u/list_simulators/stdout
Compare to a successful prod run. Both are running
12c33
.https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8823956734184440353/+/u/list_simulators/stdout
Blocking the plugin roll #97295, which is blocking an engine roll.
The text was updated successfully, but these errors were encountered: