Skip to content

[Integration test failures] service_extensions_test.dart #9646

@elliette

Description

@elliette

Failure:

FlutterDriveProcess - Launching integration_test/test/live_connection/service_extensions_test.dart on Web Server in debug mode...
FlutterDriveProcess - Waiting for connection from debug service on Web Server...         59.0s
FlutterDriveProcess - integration_test/test/live_connection/service_extensions_test.dart is being served at http://localhost:49602
FlutterDriveProcess - The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.
FlutterDriveProcess - Debug service listening on ws://127.0.0.1:49639/wD138VZzKuk=/ws
FlutterDriveProcess - A Dart VM Service on Web Server is available at: http://127.0.0.1:49639/wD138VZzKuk=
FlutterDriveProcess - The Flutter DevTools debugger and profiler on Web Server is available at: http://127.0.0.1:49639/wD138VZzKuk=/devtools/?uri=ws://127.0.0.1:49639/wD138VZzKuk=/ws
FlutterDriveProcess - result {"result":"true","failureDetails":[]}
FlutterDriveProcess - All tests passed.
FlutterDriveProcess - Application finished.
FlutterDriveProcess - Resolving dependencies in `/Users/runner/work/devtools/devtools`...
FlutterDriveProcess - Downloading packages...
FlutterDriveProcess -   _fe_analyzer_shared 91.0.0 (94.0.0 available)
FlutterDriveProcess -   analyzer 8.4.1 (10.0.2 available)
FlutterDriveProcess -   build 4.0.3 (4.0.4 available)
FlutterDriveProcess -   build_runner 2.10.4 (2.10.5 available)
FlutterDriveProcess -   built_value 8.12.1 (8.12.3 available)
FlutterDriveProcess -   code_builder 4.11.0 (4.11.1 available)
FlutterDriveProcess -   cross_file 0.3.5+1 (0.3.5+2 available)
FlutterDriveProcess -   dart_style 3.1.3 (3.1.5 available)
FlutterDriveProcess -   ffi 2.1.4 (2.1.5 available)
FlutterDriveProcess -   flutter_lints 5.0.0 (6.0.0 available)
FlutterDriveProcess -   image 4.5.4 (4.7.2 available)
FlutterDriveProcess -   intl 0.19.0 (0.20.2 available)
FlutterDriveProcess -   json_annotation 4.9.0 (4.10.0 available)
FlutterDriveProcess -   json_rpc_2 3.0.3 (4.0.0 available)
FlutterDriveProcess -   lints 5.1.1 (6.1.0 available)
FlutterDriveProcess -   meta 1.17.0 (1.18.1 available)
FlutterDriveProcess -   mockito 5.6.1 (5.6.3 available)
FlutterDriveProcess -   protobuf 5.1.0 (6.0.0 available)
FlutterDriveProcess -   source_gen 4.1.1 (4.2.0 available)
FlutterDriveProcess -   test 1.28.0 (1.29.0 available)
FlutterDriveProcess -   test_api 0.7.8 (0.7.9 available)
FlutterDriveProcess -   test_core 0.6.14 (0.6.15 available)
FlutterDriveProcess -   unified_analytics 7.0.2 (8.0.10 available)
FlutterDriveProcess -   url_launcher_web 2.4.1 (2.4.2 available)
FlutterDriveProcess -   watcher 1.1.4 (1.2.1 available)
FlutterDriveProcess -   web_benchmarks 4.0.0 (4.1.0 available)
FlutterDriveProcess - Got dependencies in `/Users/runner/work/devtools/devtools`!
FlutterDriveProcess - 26 packages have newer versions incompatible with dependency constraints.
FlutterDriveProcess - Try `flutter pub outdated` for more information.
FlutterDriveProcess - Launching integration_test/test/live_connection/app_test.dart on Web Server in debug mode...
FlutterDriveProcess - Waiting for connection from debug service on Web Server...         52.0s
FlutterDriveProcess - integration_test/test/live_connection/app_test.dart is being served at http://localhost:49661
FlutterDriveProcess - The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.
FlutterDriveProcess - Debug service listening on ws://127.0.0.1:49695/Ur-aHpSdO9o=/ws
FlutterDriveProcess - A Dart VM Service on Web Server is available at: http://127.0.0.1:49695/Ur-aHpSdO9o=
FlutterDriveProcess - The Flutter DevTools debugger and profiler on Web Server is available at: http://127.0.0.1:49695/Ur-aHpSdO9o=/devtools/?uri=ws://127.0.0.1:49695/Ur-aHpSdO9o=/ws
FlutterDriveProcess - result {"result":"false","failureDetails":["{\"methodName\":\"connect to app and switch tabs\",\"details\":\"══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════\\nThe following message was thrown:\\nMultiple exceptions (3) were detected during the running of the\\ncurrent test, and at least one was unexpected.\\n═════════════════════════════════════════════════════════════════\\n\"}"]}
FlutterDriveProcess - Failure Details:
FlutterDriveProcess - Failure in method: connect to app and switch tabs
FlutterDriveProcess - ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
FlutterDriveProcess - The following message was thrown:
FlutterDriveProcess - Multiple exceptions (3) were detected during the running of the
FlutterDriveProcess - current test, and at least one was unexpected.
FlutterDriveProcess - ═════════════════════════════════════════════════════════════════
FlutterDriveProcess - 
FlutterDriveProcess - end of failure 1
FlutterDriveProcess - 
FlutterDriveProcess - 
FlutterDriveProcess - 
FlutterDriveProcess - Application finished.
Unhandled exception:
Exception: Test 'connect to app and switch tabs' failed: ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
The following message was thrown:
Multiple exceptions (3) were detected during the running of the
current test, and at least one was unexpected.
═════════════════════════════════════════════════════════════════
.

result {"result":"false","failureDetails":["{\"methodName\":\"connect to app and switch tabs\",\"details\":\"══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════\\nThe following message was thrown:\\nMultiple exceptions (3) were detected during the running of the\\ncurrent test, and at least one was unexpected.\\n═════════════════════════════════════════════════════════════════\\n\"}"]}
Failure Details:
Failure in method: connect to app and switch tabs
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
The following message was thrown:
Multiple exceptions (3) were detected during the running of the
current test, and at least one was unexpected.
═════════════════════════════════════════════════════════════════


#0      IntegrationTestRunner.run.runTest (package:devtools_shared/src/test/integration_test_runner.dart:154:11)
<asynchronous suspension>
#1      IntegrationTestRunner.run (package:devtools_shared/src/test/integration_test_runner.dart:160:5)
<asynchronous suspension>
#2      runFlutterIntegrationTest (file:///Users/runner/work/devtools/devtools/packages/devtools_app/integration_test/test_infra/run/run_test.dart:81:5)
<asynchronous suspension>
#3      _runTest (file:///Users/runner/work/devtools/devtools/packages/devtools_app/integration_test/run_tests.dart:92:3)
<asynchronous suspension>
#4      runOneOrManyTests (package:devtools_shared/src/test/integration_test_runner.dart:354:9)
<asynchronous suspension>
#5      main (file:///Users/runner/work/devtools/devtools/packages/devtools_app/integration_test/run_tests.dart:61:3)
<asynchronous suspension>
Error: Process completed with exit code 255.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1high priority issues at the top of the work list, actively being worked on.integration tests

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions