Skip to content

Flaky flutter drive test on Moto G4 with --trace-startup #59263

@CareF

Description

@CareF

Very often when I run flutter drive for a test case in macrobenchmarks, with option --trace-startup (which is the case we run for devicelab. This issue is talking about running locally though.), the app crashes on the device with message "Unfortunately, macrobenchmarks has stopped." resulting in test fail. This only happens to Moto G4 but not Pixel 4.
The notice on host machine shows:

VMServiceFlutterDriver: Instance of '_WebSocketImpl' is closed with an unexpected code 1005
VMServiceFlutterDriver: Instance of '_WebSocketImpl' is closed with an unexpected code 1005

Any suggestion about what can check is appreciated!

Metadata

Metadata

Assignees

No one assigned

    Labels

    a: tests"flutter test", flutter_test, or one of our testsr: invalidIssue is closed as not validt: flutter driver"flutter driver", flutter_drive, or a driver testtoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions