Jenn Magder

Let's track the observatory timeouts in https://github.com/flutter/flutter/issues/121231.

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios_simulator/1831 is a `webdriver` pub blip where all the package GETs were 404s, we can probably ignore: ``` [hot_mode_dev_cycle_ios_simulator] [STDOUT] stderr: IO : HTTP response 404 Not Found for GET...

Dropping down to P4 since this has been seen a few times, but not with a frequency that has cause the flake percentage to go over the threshold.

@a-siva let's do that, I had forgotten this one was still hanging out.

Hm, 4094 and 4171 lost connection to device, not sure what that's about? It ran on different devicelab bots. ``` [hot_mode_dev_cycle_ios__benchmark] [STDOUT] stdout: [+21099 ms] (lldb) warning: failed to set...

The lost connection sounds like the app is taking a long time to launch. It looks like it's possible to increase this lldb timeout via `settings set plugin.process.gdb-remote.packet-timeout` which we...

> 4201 and 4200 are Dart VM GC crashers on the host Tracking in https://github.com/flutter/flutter/issues/121705 > 4233 is an Observatory discovery timeout Tracking in https://github.com/flutter/flutter/issues/121709 As Zach said, let's just...

Taking screenshot on failures where it doesn't time out: https://github.com/flutter/flutter/pull/122249

https://github.com/flutter/flutter/pull/122249 is approved, was waiting for tests to pass, then we should have more info on the next bot update.

1866 is lost connection, but unfortunately it ran before https://github.com/flutter/flutter/pull/122249 merged, so no additional screenshots. The rest are observatory timeouts tracked in https://github.com/flutter/flutter/issues/121231.