Skip to content

[Browser] System.InvalidOperationException: A command response was not received: Target.setAutoAttach #130054

Open

Description

@jkotas
[17:11:42] info: Closing 1 browser tabs before setting the main tab to config page and quitting.
[17:11:54] crit: OpenQA.Selenium.WebDriverException: Unexpected error creating WebSocket DevTools session.
                  ---> System.InvalidOperationException: A command response was not received: Target.setAutoAttach
                    at OpenQA.Selenium.DevTools.DevToolsSession.SendCommand(String commandName, JToken params, CancellationToken cancellationToken, Nullable`1 millisecondsTimeout, Boolean throwExceptionIfResponseNotReceived)
                    at OpenQA.Selenium.DevTools.DevToolsSession.SendCommand[TCommand,TCommandResponse](TCommand command, CancellationToken cancellationToken, Nullable`1 millisecondsTimeout, Boolean throwExceptionIfResponseNotReceived)
                    at OpenQA.Selenium.DevTools.Target.TargetAdapter.SetAutoAttach(SetAutoAttachCommandSettings command, CancellationToken cancellationToken, Nullable`1 millisecondsTimeout, Boolean throwExceptionIfResponseNotReceived)
                    at OpenQA.Selenium.Chromium.ChromiumDriver.CreateDevToolsSession()
                    --- End of inner exception stack trace ---
                    at OpenQA.Selenium.Chromium.ChromiumDriver.CreateDevToolsSession()
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmBrowserTestRunner.RunTestsWithWebDriver(DriverService driverService, IWebDriver driver) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmBrowserTestRunner.cs:line 75
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestBrowserCommand.InvokeInternal(ILogger logger) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmTestBrowserCommand.cs:line 86
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestBrowserCommand.InvokeInternal(ILogger logger) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmTestBrowserCommand.cs:line 152
                    at Microsoft.DotNet.XHarness.CLI.Commands.XHarnessCommand`1.Invoke(IEnumerable`1 arguments) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/XHarnessCommand.cs:line 145
XHarness exit code: 71 (GENERAL_FAILURE)

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1488119
Build error leg or test failing: WasmTestOnChrome-CLR-ST-Batch-2.WorkItemExecution
Pull request: #130015

Error Message

DO NOT USE JSON BELOW IF THIS IS A BUILD BREAK otherwise build analysis will allow pull requests to merge that break the build worse. For a build break, do not use this issue form. Make a regular new issue.

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "System.InvalidOperationException: A command response was not received: Target.setAutoAttach",
  "ErrorPattern": "",
  "BuildRetry": true,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1488119
Error message validated: [System.InvalidOperationException: A command response was not received: Target.setAutoAttach]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/30/2026 8:00:12 PM UTC

Report

Build Repository Test Pull Request
1488119 dotnet/runtime WasmTestOnChrome-CLR-ST-Batch-2.WorkItemExecution #130015

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

Activity

  1. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jun 30, 2026
  2. changed the title [-][Brower] System.InvalidOperationException: A command response was not received: Target.setAutoAttach[/-] [+][Browser] System.InvalidOperationException: A command response was not received: Target.setAutoAttach[/+] on Jun 30, 2026
  3. dotnet-policy-service commented on Jun 30, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
    See info in area-owners.md if you want to be subscribed.

  4. added this to the Future milestone on Jul 2, 2026
  5. added
    arch-wasmWebAssembly architecture
    and removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 2, 2026
  6. dotnet-policy-service commented on Jul 2, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
    See info in area-owners.md if you want to be subscribed.

  7. pavelsavara commented on Jul 2, 2026

    @pavelsavara
    Member

    This is chrome/infra. I changed it to "BuildRetry": true,

  8. removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Jul 31, 2026
  9. jeffschwMSFT commented on Jul 31, 2026

    @jeffschwMSFT
    Member

    removing blocking-clean-ci as it has not failed in 30 days

    Summary
    24-Hour | Hit Count | 7-Day Hit Count | 1-Month Count
    0 | 0 |0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions