Skip to content

Intermittent failures in web_tool_tests due to failure to connect to chrome #86370

Closed as not planned
Closed as not planned
Intermittent failures in web_tool_tests due to failure to connect to chrome#86370
Labels
P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.team-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool team

Description

@annagrin
annagrin
opened on Jul 13, 2021

The failures happened in HHH flutter web bot (running heads of engine, flutter, and dart SDK) that runs flutter web_tool_tests.

Related: #85043
Example: https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/flutter-engine-linux/13586/overview

  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:328:7)
  <asynchronous suspension>
  #2      AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:595:9)
  <asynchronous suspension>
  #3      AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:593:5)
...

Activity

  1. annagrin
    changed the title [-]HHH web bot: Intermittent failures in web_tool_tests due to failure to connect to chrome[/-] [+]Intermittent failures in web_tool_tests due to failure to connect to chrome[/+] on Jul 13, 2021

  2. annagrin commented on Jul 13, 2021

    @annagrin
    annagrin
    on Jul 13, 2021
    ContributorAuthor

    /cc @jonahwilliams would it be possible to add verbose logging in throwToolExit, so we can pinpoint the failing code? I suspect something fails in dwds but cannot repro this locally.

  3. TahaTesser
    added
    in triagePresently being triaged by the triage team
    passed first triage
    toolAffects the "flutter" command-line tool. See also t: labels.
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    and removed
    in triagePresently being triaged by the triage team
    on Jul 14, 2021
  4. flutter-triage-bot
    added
    team-toolOwned by Flutter Tool team
    on Jul 8, 2023
  5. Hixie
    removed
    passed first triage
    on Jul 8, 2023
  6. christopherfujino
    added
    triaged-toolTriaged by Flutter Tool team
    P2Important issues not at the top of the work list
    on Aug 29, 2023
  7. matanlurey
    closed this as not plannedon Jul 10, 2025

  8. github-actions commented on Jul 24, 2025

    @github-actions
    github-actionsbot
    on Jul 24, 2025 – with GitHub Actions

    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.

  9. github-actions
    locked as resolved and limited conversation to collaborators on Jul 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.team-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions