Failures in integration_test-based tests run via driver don't fail the step #60943
Description
[...]
xvfb-run ./script/incremental_build.sh drive-examples --linux
Checking for changed packages from d3ccc34855b77afae39f4078cb4add8bec9e6b2b
Detected changes in the following 1 package(s):
url_launcher
running drive-examples --linux
Starting application: test_driver/url_launcher_e2e.dart
Building Linux application...
flutter: Observatory listening on http://127.0.0.1:36053/2ki0Gnu5d48=/
flutter: 00:00 +0: canLaunch
flutter: 00:00 +0: canLaunch [E]
flutter: Expected: <true>
Actual: <false>
flutter: [...]
flutter: 00:00 +0 -1: (tearDownAll)
flutter: Warning: E2E test plugin was not detected.
flutter: 00:00 +1 -1: Some tests failed.
Stopping application instance.
VMServiceFlutterDriver: Connecting to Flutter application at http://127.0.0.1:36053/2ki0Gnu5d48=/
VMServiceFlutterDriver: Isolate found with number: 3840818254652015
VMServiceFlutterDriver: Isolate is not paused. Assuming application is ready.
VMServiceFlutterDriver: Connected to Flutter application.
All driver tests successful!
Clearly flutter: 00:00 +1 -1: Some tests failed shouldn't lead to All driver tests successful! and a green CI result on the PR.
I don't know if this is a general problem, or specific to Linux somehow; I'll mark it as Linux until we know if it happens elsewhere.