Mac/Android tests timing out on "Waiting for observatory port to be available..."

Examples:

[flutter_view__start_up] [STDOUT] stdout: [   +6 ms] Launching lib/main.dart on Moto G 4 in profile mode...
[flutter_view__start_up] [STDOUT] stdout: [   +3 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R shell -x logcat -v time -t 1
[flutter_view__start_up] [STDOUT] stdout: [  +63 ms] --------- beginning of system
[flutter_view__start_up] [STDOUT] stdout:            03-01 09:30:21.991 I/WindowManager( 1540): Destroying surface Surface(name=Starting com.google.android.googlequicksearchbox) called by com.android.server.wm.WindowStateAnimator.destroySurface:2069 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:897 com.android.server.wm.WindowState.destroyOrSaveSurface:2121 com.android.server.wm.AppWindowToken.destroySurfaces:363 com.android.server.wm.WindowStateAnimator.finishExit:575 com.android.server.wm.WindowStateAnimator.stepAnimationLocked:501 com.android.server.wm.WindowAnimator.updateWindowsLocked:303 com.android.server.wm.WindowAnimator.animateLocked:704
[flutter_view__start_up] [STDOUT] stdout: [  +10 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb version
[flutter_view__start_up] [STDOUT] stdout: [   +5 ms] Android Debug Bridge version 1.0.41
[flutter_view__start_up] [STDOUT] stdout:            Version 29.0.2-5738569
[flutter_view__start_up] [STDOUT] stdout:            Installed as /opt/s/w/ir/cache/android/platform-tools/adb
[flutter_view__start_up] [STDOUT] stdout: [   +2 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb start-server
[flutter_view__start_up] [STDOUT] stdout: [   +6 ms] Stopping app 'app-profile.apk' on Moto G 4.
[flutter_view__start_up] [STDOUT] stdout: [   +1 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R shell am force-stop io.flutter.examples.flutter_view
[flutter_view__start_up] [STDOUT] stdout: [ +880 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R shell pm list packages io.flutter.examples.flutter_view
[flutter_view__start_up] [STDOUT] stdout: [ +936 ms] Installing APK.
[flutter_view__start_up] [STDOUT] stdout: [   +4 ms] Installing build/app/outputs/flutter-apk/app-profile.apk...
[flutter_view__start_up] [STDOUT] stdout: [        ] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R install -t -r /opt/s/w/ir/k/recipe_cleanup/tmpfZcGdz/flutter sdk/examples/flutter_view/build/app/outputs/flutter-apk/app-profile.apk
[flutter_view__start_up] [STDOUT] stdout: [+5320 ms] Performing Streamed Install
[flutter_view__start_up] [STDOUT] stdout:            Success
[flutter_view__start_up] [STDOUT] stdout: [  +12 ms] Installing build/app/outputs/flutter-apk/app-profile.apk... (completed in 5.3s)
[flutter_view__start_up] [STDOUT] stdout: [        ] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R shell echo -n  > /data/local/tmp/sky.io.flutter.examples.flutter_view.sha1
[flutter_view__start_up] [STDOUT] stdout: [  +40 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R shell -x logcat -v time -t 1
[flutter_view__start_up] [STDOUT] stdout: [  +86 ms] --------- beginning of main
[flutter_view__start_up] [STDOUT] stdout:            03-01 09:30:29.934 I/Finsky  ( 6740): [467] qod.run(-1): Wrote row to frosting DB: 25210
[flutter_view__start_up] [STDOUT] stdout: [   +5 ms] executing: /opt/s/w/ir/cache/android/platform-tools/adb -s ZY223J893R shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation true --ez enable-dart-profiling true --ez trace-startup true io.flutter.examples.flutter_view/com.example.view.MainActivity
[flutter_view__start_up] [STDOUT] stdout: [ +911 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=io.flutter.examples.flutter_view/com.example.view.MainActivity (has extras) }
[flutter_view__start_up] [STDOUT] stdout: [        ] Waiting for observatory port to be available...

@jonahwilliams

\cc @jonahwilliams @jmagman

@goderbauer

cc @goderbauer

@xster

cc @xster

These tests pass locally for me on a Pixel 4.

Task result:
{
  "success": true,
  "data": {
    "engineEnterTimestampMicros": 71377194,
    "timeToFrameworkInitMicros": 88608,
    "timeToFirstFrameRasterizedMicros": 307352,
    "timeToFirstFrameMicros": 208231,
    "timeAfterFrameworkInitMicros": 119622
  },
  "detailFiles": [],
  "benchmarkScoreKeys": [],
  "reason": "success"
}


═══════════════╡ ••• Finished task "flutter_view__start_up" ••• ╞═══════════════
}

@godofredoc

@godofredoc These are failing on the Moto G4s, with a macOS host, right?

yes, that is correct.

I think it's going to be hard to archeologize this from the old run instances now since it's not reproducible and the flake rate since those runs in the last month is bad but not blocking.

We should certainly improve on this. I'd recommend continuing on #79097 to take more actions in the future since it's likely hard to extract more todos from the old logs. Dan's timeline dump could likely help categorize and break this cluster down more. I think we can do an adb logcat dump too on the side to help more.

@jonahwilliams

@jonahwilliams do you know if something like your change in #77193 (comment) ever landed?

No, I haven't landed anything that changed stopApp around.

that said I did re-discover that we need an attached device for attach, which is wrong, but it means we could easily make the switch with no regressions today.

Another failed build: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android%20microbenchmarks/1367/overview

@jonahwilliams

Are we getting logs from the device on these failures? I didn't think we needed a VM service connection on Android to get the device logs. Either way, since I think there hasn't been any fix for this landed anywhere, we should assume that the cause is the same as above.

@jonahwilliams Is the issue with attach a blocker for re-ordering device.stopApp and vmService.flutterExit?

There is no issue with attach since we require a device. LMK and I can change the behavior here

Yes, let's do it =) Thanks.

on it

is anything changed here related to recent TOT failures? More than 10 tests failed with timeout on Waiting for observatory port to be available

That is a different failure caused by a bad engine roll

I haven't seen this issue recently, please reopen if you find it again.

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 flutter doctor -v and a minimal reproduction of the issue.

Navigation Menu

Repository navigation

Mac/Android tests timing out on "Waiting for observatory port to be available..." #77193

44 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Mac/Android tests timing out on "Waiting for observatory port to be available..." #77193

Description

Activity

godofredoc commented on Mar 4, 2021

Hixie commented on Mar 9, 2021

Hixie commented on Mar 17, 2021

jmagman commented on Mar 17, 2021

Hixie commented on Mar 23, 2021

godofredoc commented on Mar 23, 2021

xster commented on Mar 31, 2021

44 remaining items

zanderso commented on May 20, 2021

jonahwilliams commented on May 20, 2021

jonahwilliams commented on May 20, 2021

keyonghan commented on Jun 2, 2021

zanderso commented on Jun 2, 2021

jonahwilliams commented on Jun 2, 2021

zanderso commented on Jun 2, 2021

jonahwilliams commented on Jun 2, 2021

keyonghan commented on Jun 3, 2021

jonahwilliams commented on Jun 3, 2021

godofredoc commented on Sep 24, 2021

github-actions commented on Oct 8, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions