Engine roll causing observatory connection timeouts on 32-bit iPhones #40114
Description
I reverted two engine rolls in #40112 because the were causing failures in devicelab tests that were failing with timeouts trying to connect to the observatory: flutter_gallery_ios32__transition_perf and flutter_gallery_ios32__start_up.
I HAVE STOPPED THE ENGINE ROLL, so someone needs to restart it once this is resolved.
Specifically, they started failing when af07bb5 was committed, which includes a Dart roll that is probably suspect:
2019-09-06 [email protected] Roll src/third_party/dart be66176534..ec7ec4ecf7 (37 commits)
Here is a sample log output of one of the tests (both are similar):
2019-09-09T14:09:01.547976: stdout: [ +40 ms] (lldb) run
2019-09-09T14:09:03.005319: stdout: [+1457 ms] success
stdout: [ ] (lldb) safequit
2019-09-09T14:09:03.132474: stdout: [ +125 ms] Process 248 detached
2019-09-09T14:09:03.159828: stdout: [ +28 ms] Application launched on the device. Waiting for observatory port.
2019-09-09T14:21:27.297237: Task timed out in framework.dart after 0:15:00.000000.
Cleaning up after task...
2019-09-09T14:21:28.310369: Force-quitting process:
command : bin/flutter run --verbose --profile --trace-startup -d [device id redacted]
started : 2019-09-09 14:06:29.482349
pid : 12227
2019-09-09T14:21:28.318085: "bin/flutter" exit code: -15
2019-09-09T14:21:29.329736: Task execution finished
Task failed with the following reason:
Timeout waiting for task process to exit: Future not completed