[Integration test failures] network_screen_test.dart #9639
Description
Failure:
FlutterDriveProcess - Launching integration_test/test/live_connection/network_screen_test.dart on Web Server in debug mode...
FlutterDriveProcess - Waiting for connection from debug service on Web Server... 63.6s
FlutterDriveProcess - integration_test/test/live_connection/network_screen_test.dart is being served at http://localhost:49481
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:49515/gE-49Eo-AQk=/ws
FlutterDriveProcess - A Dart VM Service on Web Server is available at: http://127.0.0.1:49515/gE-49Eo-AQk=
FlutterDriveProcess - The Flutter DevTools debugger and profiler on Web Server is available at: http://127.0.0.1:49515/gE-49Eo-AQk=/devtools/?uri=ws://127.0.0.1:49515/gE-49Eo-AQk=/ws
FlutterDriveProcess - result {"result":"false","failureDetails":["{\"methodName\":\"network screen test\",\"details\":\"══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞══════════════════════\\nThe following assertion was thrown during a scheduler callback:\\nInvisible SemanticsNodes should not be added to the tree.\\nThe following invisible SemanticsNodes were added to the tree:\\nSemanticsNode#107(Rect.fromLTRB(1461.0, 5.0, 1489.0, 25.0), flags: [isButton, hasEnabledState, isEnabled, isFocusable])\\nwhich was added as a child of:\\n SemanticsNode#108(Rect.fromLTRB(1401.0, 5.0, 1489.0, 25.0), tags: [_InputDecoratorState.suffixIcon], traversalParentIdentifier: _OverlayPortalState#6269d(lifecycle state: defunct, not mounted), tooltip: \\\"Help\\\", textDirection: ltr)\\nAn invisible SemanticsNode is one whose rect is not on screen\\nhence not reachable for users, and its semantic information is\\nnot merged into a visible parent.\\nAn invisible SemanticsNode makes the accessibility experience\\nconfusing, as it does not provide any visual indication when the\\nuser selects it via accessibility technologies.\\nConsider removing the above invisible SemanticsNodes if they were\\nadded by your RenderObject.assembleSemanticsNode implementation,\\nor filing a bug on GitHub:\\n https://github.com/flutter/flutter/issues/new?template=02_bug.yml\\n\\nWhen the exception was thrown, this was the stack:\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 274:3 throw_\\npackage:flutter/src/semantics/semantics.dart 4860:7 <fn>\\npackage:flutter/src/semantics/semantics.dart 4860:53 sendSemanticsUpdate\\npackage:flutter/src/rendering/object.dart 1516:7 flushSemantics\\npackage:flutter/src/rendering/object.dart 1518:14 flushSemantics\\npackage:flutter/src/rendering/binding.dart 636:7 drawFrame\\npackage:flutter/src/widgets/binding.dart 1269:13 drawFrame\\npackage:flutter/src/rendering/binding.dart 495:5 [_handlePersistentFrameCallback]\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear\\npackage:flutter/src/scheduler/binding.dart 1430:7 [_invokeFrameCallback]\\npackage:flutter/src/scheduler/binding.dart 1345:9 handleDrawFrame\\npackage:flutter_test/src/binding.dart 2388:13 handleDrawFrame\\npackage:flutter/src/scheduler/binding.dart 1198:5 [_handleDrawFrame]\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear\\nlib/_engine/engine/platform_dispatcher.dart 1689:5 invoke\\nlib/_engine/engine/platform_dispatcher.dart 265:5 invokeOnDrawFrame\\nlib/_engine/engine/frame_service.dart 209:32 [_renderFrame]\\nlib/_engine/engine/frame_service.dart 117:9 <fn>\\ndart-sdk/lib/async/zone_root.dart 56:13 _rootRunUnary\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear\\ndart-sdk/lib/async/zone.dart 733:19 runUnary\\ndart-sdk/lib/async/zone.dart 654:26 <fn>\\ndart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 224:27 _callDartFunctionFast1\\ndart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 84:15 ret\\n═════════════════════════════════════════════════════════════════\\n\"}"]}
FlutterDriveProcess - Failure Details:
FlutterDriveProcess - Failure in method: network screen test
FlutterDriveProcess - ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞══════════════════════
FlutterDriveProcess - The following assertion was thrown during a scheduler callback:
FlutterDriveProcess - Invisible SemanticsNodes should not be added to the tree.
FlutterDriveProcess - The following invisible SemanticsNodes were added to the tree:
FlutterDriveProcess - SemanticsNode#107(Rect.fromLTRB(1461.0, 5.0, 1489.0, 25.0), flags: [isButton, hasEnabledState, isEnabled, isFocusable])
FlutterDriveProcess - which was added as a child of:
FlutterDriveProcess - SemanticsNode#108(Rect.fromLTRB(1401.0, 5.0, 1489.0, 25.0), tags: [_InputDecoratorState.suffixIcon], traversalParentIdentifier: _OverlayPortalState#6269d(lifecycle state: defunct, not mounted), tooltip: "Help", textDirection: ltr)
FlutterDriveProcess - An invisible SemanticsNode is one whose rect is not on screen
FlutterDriveProcess - hence not reachable for users, and its semantic information is
FlutterDriveProcess - not merged into a visible parent.
FlutterDriveProcess - An invisible SemanticsNode makes the accessibility experience
FlutterDriveProcess - confusing, as it does not provide any visual indication when the
FlutterDriveProcess - user selects it via accessibility technologies.
FlutterDriveProcess - Consider removing the above invisible SemanticsNodes if they were
FlutterDriveProcess - added by your RenderObject.assembleSemanticsNode implementation,
FlutterDriveProcess - or filing a bug on GitHub:
FlutterDriveProcess - https://github.com/flutter/flutter/issues/new?template=02_bug.yml
FlutterDriveProcess -
FlutterDriveProcess - When the exception was thrown, this was the stack:
FlutterDriveProcess - dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 274:3 throw_
FlutterDriveProcess - package:flutter/src/semantics/semantics.dart 4860:7 <fn>
FlutterDriveProcess - package:flutter/src/semantics/semantics.dart 4860:53 sendSemanticsUpdate
FlutterDriveProcess - package:flutter/src/rendering/object.dart 1516:7 flushSemantics
FlutterDriveProcess - package:flutter/src/rendering/object.dart 1518:14 flushSemantics
FlutterDriveProcess - package:flutter/src/rendering/binding.dart 636:7 drawFrame
FlutterDriveProcess - package:flutter/src/widgets/binding.dart 1269:13 drawFrame
FlutterDriveProcess - package:flutter/src/rendering/binding.dart 495:5 [_handlePersistentFrameCallback]
FlutterDriveProcess - dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
FlutterDriveProcess - package:flutter/src/scheduler/binding.dart 1430:7 [_invokeFrameCallback]
FlutterDriveProcess - package:flutter/src/scheduler/binding.dart 1345:9 handleDrawFrame
FlutterDriveProcess - package:flutter_test/src/binding.dart 2388:13 handleDrawFrame
FlutterDriveProcess - package:flutter/src/scheduler/binding.dart 1198:5 [_handleDrawFrame]
FlutterDriveProcess - dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
FlutterDriveProcess - lib/_engine/engine/platform_dispatcher.dart 1689:5 invoke
FlutterDriveProcess - lib/_engine/engine/platform_dispatcher.dart 265:5 invokeOnDrawFrame
FlutterDriveProcess - lib/_engine/engine/frame_service.dart 209:32 [_renderFrame]
FlutterDriveProcess - lib/_engine/engine/frame_service.dart 117:9 <fn>
FlutterDriveProcess - dart-sdk/lib/async/zone_root.dart 56:13 _rootRunUnary
FlutterDriveProcess - dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
FlutterDriveProcess - dart-sdk/lib/async/zone.dart 733:19 runUnary
FlutterDriveProcess - dart-sdk/lib/async/zone.dart 654:26 <fn>
FlutterDriveProcess - dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 224:27 _callDartFunctionFast1
FlutterDriveProcess - dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 84:15 ret
FlutterDriveProcess - ═════════════════════════════════════════════════════════════════
FlutterDriveProcess -
FlutterDriveProcess - end of failure 1
FlutterDriveProcess -
FlutterDriveProcess -
FlutterDriveProcess -
FlutterDriveProcess - Application finished.
Unhandled exception:
Exception: Test 'network screen test' failed: ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞══════════════════════
The following assertion was thrown during a scheduler callback:
Invisible SemanticsNodes should not be added to the tree.
The following invisible SemanticsNodes were added to the tree:
SemanticsNode#107(Rect.fromLTRB(1461.0, 5.0, 1489.0, 25.0), flags: [isButton, hasEnabledState, isEnabled, isFocusable])
which was added as a child of:
SemanticsNode#108(Rect.fromLTRB(1401.0, 5.0, 1489.0, 25.0), tags: [_InputDecoratorState.suffixIcon], traversalParentIdentifier: _OverlayPortalState#6269d(lifecycle state: defunct, not mounted), tooltip: "Help", textDirection: ltr)
An invisible SemanticsNode is one whose rect is not on screen
hence not reachable for users, and its semantic information is
not merged into a visible parent.
An invisible SemanticsNode makes the accessibility experience
confusing, as it does not provide any visual indication when the
user selects it via accessibility technologies.
Consider removing the above invisible SemanticsNodes if they were
added by your RenderObject.assembleSemanticsNode implementation,
or filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=02_bug.yml
When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 274:3 throw_
package:flutter/src/semantics/semantics.dart 4860:7 <fn>
package:flutter/src/semantics/semantics.dart 4860:53 sendSemanticsUpdate
package:flutter/src/rendering/object.dart 1516:7 flushSemantics
package:flutter/src/rendering/object.dart 1518:14 flushSemantics
package:flutter/src/rendering/binding.dart 636:7 drawFrame
package:flutter/src/widgets/binding.dart 1269:13 drawFrame
package:flutter/src/rendering/binding.dart 495:5 [_handlePersistentFrameCallback]
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
package:flutter/src/scheduler/binding.dart 1430:7 [_invokeFrameCallback]
package:flutter/src/scheduler/binding.dart 1345:9 handleDrawFrame
package:flutter_test/src/binding.dart 2388:13 handleDrawFrame
package:flutter/src/scheduler/binding.dart 1198:5 [_handleDrawFrame]
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
lib/_engine/engine/platform_dispatcher.dart 1689:5 invoke
lib/_engine/engine/platform_dispatcher.dart 265:5 invokeOnDrawFrame
lib/_engine/engine/frame_service.dart 209:32 [_renderFrame]
lib/_engine/engine/frame_service.dart 117:9 <fn>
dart-sdk/lib/async/zone_root.dart 56:13 _rootRunUnary
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
dart-sdk/lib/async/zone.dart 733:19 runUnary
dart-sdk/lib/async/zone.dart 654:26 <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 224:27 _callDartFunctionFast1
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 84:15 ret
═════════════════════════════════════════════════════════════════
.
result {"result":"false","failureDetails":["{\"methodName\":\"network screen test\",\"details\":\"══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞══════════════════════\\nThe following assertion was thrown during a scheduler callback:\\nInvisible SemanticsNodes should not be added to the tree.\\nThe following invisible SemanticsNodes were added to the tree:\\nSemanticsNode#107(Rect.fromLTRB(1461.0, 5.0, 1489.0, 25.0), flags: [isButton, hasEnabledState, isEnabled, isFocusable])\\nwhich was added as a child of:\\n SemanticsNode#108(Rect.fromLTRB(1401.0, 5.0, 1489.0, 25.0), tags: [_InputDecoratorState.suffixIcon], traversalParentIdentifier: _OverlayPortalState#6269d(lifecycle state: defunct, not mounted), tooltip: \\\"Help\\\", textDirection: ltr)\\nAn invisible SemanticsNode is one whose rect is not on screen\\nhence not reachable for users, and its semantic information is\\nnot merged into a visible parent.\\nAn invisible SemanticsNode makes the accessibility experience\\nconfusing, as it does not provide any visual indication when the\\nuser selects it via accessibility technologies.\\nConsider removing the above invisible SemanticsNodes if they were\\nadded by your RenderObject.assembleSemanticsNode implementation,\\nor filing a bug on GitHub:\\n https://github.com/flutter/flutter/issues/new?template=02_bug.yml\\n\\nWhen the exception was thrown, this was the stack:\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 274:3 throw_\\npackage:flutter/src/semantics/semantics.dart 4860:7 <fn>\\npackage:flutter/src/semantics/semantics.dart 4860:53 sendSemanticsUpdate\\npackage:flutter/src/rendering/object.dart 1516:7 flushSemantics\\npackage:flutter/src/rendering/object.dart 1518:14 flushSemantics\\npackage:flutter/src/rendering/binding.dart 636:7 drawFrame\\npackage:flutter/src/widgets/binding.dart 1269:13 drawFrame\\npackage:flutter/src/rendering/binding.dart 495:5 [_handlePersistentFrameCallback]\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear\\npackage:flutter/src/scheduler/binding.dart 1430:7 [_invokeFrameCallback]\\npackage:flutter/src/scheduler/binding.dart 1345:9 handleDrawFrame\\npackage:flutter_test/src/binding.dart 2388:13 handleDrawFrame\\npackage:flutter/src/scheduler/binding.dart 1198:5 [_handleDrawFrame]\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear\\nlib/_engine/engine/platform_dispatcher.dart 1689:5 invoke\\nlib/_engine/engine/platform_dispatcher.dart 265:5 invokeOnDrawFrame\\nlib/_engine/engine/frame_service.dart 209:32 [_renderFrame]\\nlib/_engine/engine/frame_service.dart 117:9 <fn>\\ndart-sdk/lib/async/zone_root.dart 56:13 _rootRunUnary\\ndart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear\\ndart-sdk/lib/async/zone.dart 733:19 runUnary\\ndart-sdk/lib/async/zone.dart 654:26 <fn>\\ndart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 224:27 _callDartFunctionFast1\\ndart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 84:15 ret\\n═════════════════════════════════════════════════════════════════\\n\"}"]}
Failure Details:
Failure in method: network screen test
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞══════════════════════
The following assertion was thrown during a scheduler callback:
Invisible SemanticsNodes should not be added to the tree.
The following invisible SemanticsNodes were added to the tree:
SemanticsNode#107(Rect.fromLTRB(1461.0, 5.0, 1489.0, 25.0), flags: [isButton, hasEnabledState, isEnabled, isFocusable])
which was added as a child of:
SemanticsNode#108(Rect.fromLTRB(1401.0, 5.0, 1489.0, 25.0), tags: [_InputDecoratorState.suffixIcon], traversalParentIdentifier: _OverlayPortalState#6269d(lifecycle state: defunct, not mounted), tooltip: "Help", textDirection: ltr)
An invisible SemanticsNode is one whose rect is not on screen
hence not reachable for users, and its semantic information is
not merged into a visible parent.
An invisible SemanticsNode makes the accessibility experience
confusing, as it does not provide any visual indication when the
user selects it via accessibility technologies.
Consider removing the above invisible SemanticsNodes if they were
added by your RenderObject.assembleSemanticsNode implementation,
or filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=02_bug.yml
When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 274:3 throw_
package:flutter/src/semantics/semantics.dart 4860:7 <fn>
package:flutter/src/semantics/semantics.dart 4860:53 sendSemanticsUpdate
package:flutter/src/rendering/object.dart 1516:7 flushSemantics
package:flutter/src/rendering/object.dart 1518:14 flushSemantics
package:flutter/src/rendering/binding.dart 636:7 drawFrame
package:flutter/src/widgets/binding.dart 1269:13 drawFrame
package:flutter/src/rendering/binding.dart 495:5 [_handlePersistentFrameCallback]
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
package:flutter/src/scheduler/binding.dart 1430:7 [_invokeFrameCallback]
package:flutter/src/scheduler/binding.dart 1345:9 handleDrawFrame
package:flutter_test/src/binding.dart 2388:13 handleDrawFrame
package:flutter/src/scheduler/binding.dart 1198:5 [_handleDrawFrame]
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
lib/_engine/engine/platform_dispatcher.dart 1689:5 invoke
lib/_engine/engine/platform_dispatcher.dart 265:5 invokeOnDrawFrame
lib/_engine/engine/frame_service.dart 209:32 [_renderFrame]
lib/_engine/engine/frame_service.dart 117:9 <fn>
dart-sdk/lib/async/zone_root.dart 56:13 _rootRunUnary
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77 tear
dart-sdk/lib/async/zone.dart 733:19 runUnary
dart-sdk/lib/async/zone.dart 654:26 <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 224:27 _callDartFunctionFast1
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 84:15 ret
═════════════════════════════════════════════════════════════════
#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:84: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:53:3)
<asynchronous suspension>
Error: Process completed with exit code 255.