+huangml who is addressing capacity concerns right now.

IIUC, *both* downstream and upstream need to stop running iOS 9 tests, correct?

The relevant configs for downstream:
 https://chrome-internal.googlesource.com/chrome/ios_internal/+/master/build/bots/

(for the corresponding masters). Again, all masters should stop running iOS 9 tests, except for the new upcoming bot per  issue 778233 .

Configs upstream: https://chromium.googlesource.com/chromium/src/+/master/ios/build/bots/chromium.mac

Again, all bots need to stop running iOS 9 tests.

Do we have plan on updating iOS 9 devices?

All bots need to stop referencing iOS 9, some of them (all?) should be transfered to the new webview bot (see  https://crbug.com/778233 )

+shenghuazhang@ - Sarah, could you please take this bug? Thanks!

For downstream, I will remove ios9 related slave bots from bling masters internal.bling.main, internal.bling.fyi and internal.bling.tryserver , which is in https://chrome-internal.git.corp.google.com/chrome/tools/build/+/master/masters

Restart masters and then delete ios 9 tests suites from those bot config json files (or remove the json files). Also will unregister the ios9-related trybots names from gerrit code review ui. 

Upstream should be similar, and only saw chromium.fyi/ios-simulator-cronet and chromium.webrtc.fyi/ios-simulator have ios9 tests.

The webrtc and cronet bots should not be changed.

Hi Sarah,
Just wanted to check on timeline. Is this something that will take 1 or 2 days, or more? Do you think this task will be done by early next week?
Thanks,

Hi Lindsay, sorry for delaying on this! I worked this early this week but got sick yesterday. Working on it now and could be done by this week.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/c769ed258568e471e4d7ffeacb7d7dbd47caf31b

commit c769ed258568e471e4d7ffeacb7d7dbd47caf31b
Author: Shenghua Zhang <shenghuazhang@google.com>
Date: Thu Nov 09 22:07:45 2017

Removed iOS 9 related tryserver bots from buildbucket.config: https://chrome-internal-review.googlesource.com/c/chrome/ios_internal/+/501052

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/428e8590921e9261aef7aea04342d7f569c884e5

commit 428e8590921e9261aef7aea04342d7f569c884e5
Author: Shenghua Zhang <shenghuazhang@google.com>
Date: Thu Nov 09 23:01:30 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/f444f3d324b7270bd8dec67d3503126507921a9c

commit f444f3d324b7270bd8dec67d3503126507921a9c
Author: Shenghua Zhang <shenghuazhang@google.com>
Date: Thu Nov 09 23:54:00 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/65d14d924933cff7e809dd06288e5ea3ad2798db

commit 65d14d924933cff7e809dd06288e5ea3ad2798db
Author: Shenghua Zhang <shenghuazhang@google.com>
Date: Thu Nov 09 23:55:30 2017

Since webrtc and cronet bots cannot be touched, so upstream waterfall would be remain as what it is. 
Downstream ios9 bots are either removed or pointed the tests to iOS 11 (perf).

Mark this bug as fixed.

Thank you! @noyau please let us know if there is anything else needed here.