You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
03:01 +7 ~2 -1: test/web.shard/web_run_test.dart: flutter run works on web devices with a unary main function [E]
Exception: Exception: Received app.stop event while waiting for app.started event
[ +99 ms] SocketException: Failed to create server socket (OS Error: The shared flag to bind() needs to be `true` if binding multiple times on the same (address, port) combination.), address = ::1, port = 34463
#0 _NativeSocket.bind (dart:io-patch/socket_patch.dart:988:7)
<asynchronous suspension>
#1 HttpMultiServer._loopback (package:http_multi_server/http_multi_server.dart:183:22)
<asynchronous suspension>
#2 ExtensionBackend.start (package:dwds/src/servers/extension_backend.dart:57:18)
<asynchronous suspension>
#3 Dwds.start (package:dwds/dwds.dart:138:26)
<asynchronous suspension>
#4 WebAssetServer.start (package:flutter_tools/src/isolated/devfs_web.dart:274:23)
<asynchronous suspension>
#5 WebDevFS.create (package:flutter_tools/src/isolated/devfs_web.dart:727:22)
<asynchronous suspension>
#6 ResidentWebRunner.run.<anonymous closure> (package:flutter_tools/src/isolated/resident_web_runner.dart:285:25)
<asynchronous suspension>
#7 asyncGuard.<anonymous closure> (package:flutter_tools/src/base/async_guard.dart:111:24)
<asynchronous suspension>
Failed to establish connection with the application instance in Chrome.
This can happen if the websocket connection used by the web tooling is unable to correctly establish a connection, for example due to a firewall.
#0 throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1 ResidentWebRunner.run (package:flutter_tools/src/isolated/resident_web_runner.dart:336:7)
<asynchronous suspension>
#2 AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:599:9)
<asynchronous suspension>
#3 AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:597:5)
<asynchronous suspension>
#4 RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:558:15)
<asynchronous suspension>
#5 FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1135:27)
<asynchronous suspension>
#6 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#7 CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#8 FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#9 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10 FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#11 run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#12 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13 main (package:flutter_tools/executable.dart:93:3)
<asynchronous suspension>
👍 @annagrin is the right contact. FYI she is out a few days so this will likely not be acted on immediately. Can you clarify on the P1 prioritization, just want to align on expectations. It's my understanding that flutter-web-tools flakiness issues have been an ongoing battle and not something I expect to see it fixed so quickly.
@sigmundch Flutter's flaky test process (go/reduce_flutter_flakiness) treats tests that flake at a rate > 2% as P1 issues. This is currently the only open issue related to flutter-web-tools.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
zanderso commentedon Nov 8, 2021
The flaky error is the following:
zanderso commentedon Nov 9, 2021
@sigmundch Sorry if my information is stale, but is @annagrin still the right person to look into
dwdsissues that come up in the flutter tool?sigmundch commentedon Nov 10, 2021
👍 @annagrin is the right contact. FYI she is out a few days so this will likely not be acted on immediately. Can you clarify on the P1 prioritization, just want to align on expectations. It's my understanding that flutter-web-tools flakiness issues have been an ongoing battle and not something I expect to see it fixed so quickly.
zanderso commentedon Nov 10, 2021
@sigmundch Flutter's flaky test process (go/reduce_flutter_flakiness) treats tests that flake at a rate > 2% as P1 issues. This is currently the only open issue related to flutter-web-tools.
zanderso commentedon Nov 10, 2021
@yjbanov I believe @annagrin won't be able to take a look at this until next week. Do you know of anyone else who might be familiar with this area?
annagrin commentedon Nov 18, 2021
I see two types of errors in the logs:
failure to start dwds's extension backend
stack trace
Opened issue: dart-lang/webdev#1450
failure to connect to chrome
stack trace
Opened issue: #93889
4 remaining items
fluttergithubbot commentedon Dec 13, 2021
Current flaky ratio for the past (up to) 100 commits is 1.00%.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_tool_tests/4272
Commit: 16ec56e
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_tool_tests/4272
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20web_tool_tests
annagrin commentedon Dec 14, 2021
Changed priority to P3 since the flakiness is now below 2%.
fluttergithubbot commentedon Dec 20, 2021
Current flaky ratio for the past (up to) 100 commits is 0.00%. Flaky number: 0; total number: 100.
fluttergithubbot commentedon Dec 27, 2021
Current flaky ratio for the past (up to) 100 commits is 1.00%. Flaky number: 1; total number: 100.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_tool_tests/4463
Commit: c584a5e
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_tool_tests/4463
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20web_tool_tests
zanderso commentedon Dec 28, 2021
Build 4463 looks like the tool gets an unexpected response when trying to connect to the chrome debug port:
fluttergithubbot commentedon Jan 3, 2022
Current flaky ratio for the past (up to) 100 commits is 1.00%. Flaky number: 1; total number: 100.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_tool_tests/4463
Commit: c584a5e
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_tool_tests/4463
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20web_tool_tests
sigmundch commentedon Jan 6, 2022
Indeed - looks like build 4463 is the same as #93256 (comment) (tracked also in #94886)
fluttergithubbot commentedon Jan 10, 2022
Current flaky ratio for the past (up to) 100 commits is 0.00%. Flaky number: 0; total number: 100.
annagrin commentedon Jan 10, 2022
The remaining issue is tracked in #94886. The flakiness does not appear to be critical at this point.
zanderso commentedon Jan 10, 2022
Closing based on comment in #93256 (comment)
github-actions commentedon Jan 24, 2022
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.