The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/74d36890aeca6741c16bc69316188c0c8b0c4a01

commit 74d36890aeca6741c16bc69316188c0c8b0c4a01
Author: Menglu Huang <huangml@chromium.org>
Date: Tue Nov 07 02:20:44 2017

Remove iPhone7 iOS10 temporarily since some bots don't have it

Some swarming bots fail to find iPhone 7 iOS10 simulators. Change it to
run on iOS11 temporarily while we figuring out

Bug:  782060 
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I07fa1da31eb7483915d59f34a22bc09adf158196
Reviewed-on: https://chromium-review.googlesource.com/756357
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514358}
[modify] https://crrev.com/74d36890aeca6741c16bc69316188c0c8b0c4a01/ios/build/bots/chromium.mac/ios-simulator-full-configs.json

Caveat: I didn't actually look at the bots yet, just a high-level comment.

iOS 10 simulators are currently added as "legacy" to the Xcode installation on bots, and it's an additional installation step done by Labs. It's possible that some bots failed to install all the legacy simulators properly, I don't think we have enough visibility to monitor all the bots for all the manually installed components.

However, when issue 475693 is completed, we'll have a better and more automated story of deploying these simulators through Puppet+CIPD, and they should be more uniform across the fleet.

Since this is a P3, I suppose it's OK to block it on issue 475693 ?

Thanks Sergey!  Do we have a way to know what simulators are on those bots right now?  We don't want to lose iOS10 phone test coverage.  It'll be nice if there are other iOS10 iPhone simulators,  then we can wait for issue 475693.

Add a link of output
https://chromium-swarm.appspot.com/task?id=39acb560cc8a4310&refresh=10&show_raw=1

I don't have a ready answer to that... But if you can come up with a script / command that lists all the available simulators on a machine, I can help run it on all the bots via swarming tasks and collect the info this way.

Caveat: running tasks is easy, but summing up the info (e.g. into a spreadsheet) is the harder part, and may need some engineering. We can chat about it when I'm in, if you want.

Found some unit test tasks successfully run on iPhone 6s Plus iOS10 in m9 pool. 
build30-m9:
https://chromium-swarm.appspot.com/task?id=39a25eac8e10eb10&refresh=10&show_raw=1
build17-m9
https://chromium-swarm.appspot.com/task?id=399e5144686ca010&refresh=10&show_raw=1

I've seen some iPhone5 iOS10 as well. The problem might be specific to iPhone 7.  I'll try to use iPhone 6s Plus iOS10.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/807910bd4bad7be664519f2c83a7d89b819e2ce2

commit 807910bd4bad7be664519f2c83a7d89b819e2ce2
Author: Menglu Huang <huangml@chromium.org>
Date: Thu Nov 09 00:06:35 2017

Run EG tests on iPhone 6s Plus iOS10 on main waterfall

Bug:  782060 
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I332131e580a564a95d67ae16ec7a6b8faf833f43
Reviewed-on: https://chromium-review.googlesource.com/757025
Reviewed-by: Mike Baxley <baxley@chromium.org>
Commit-Queue: Menglu Huang <huangml@chromium.org>
Cr-Commit-Position: refs/heads/master@{#515021}
[modify] https://crrev.com/807910bd4bad7be664519f2c83a7d89b819e2ce2/ios/build/bots/chromium.mac/ios-simulator-full-configs.json

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tentatively archiving given the age of the bug. Reopen if it's still a problem.