-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
a: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsr: invalidIssue is closed as not validIssue is closed as not validt: flutter driver"flutter driver", flutter_drive, or a driver test"flutter driver", flutter_drive, or a driver testtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
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
Labels
a: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsr: invalidIssue is closed as not validIssue is closed as not validt: flutter driver"flutter driver", flutter_drive, or a driver test"flutter driver", flutter_drive, or a driver testtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.