Skip to content

WASM tests failing with Chrome failed to start #108859

Closed
Closed
WASM tests failing with Chrome failed to start#108859
Assignees
ilonatommy
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architecturearea-VM-meta-monoos-browserBrowser variant of arch-wasm
Milestone
10.0.0

Description

@ericstj
ericstj
opened on Oct 14, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=840205
Build error leg or test failing: Common.Tests.WorkItemExecution
Pull request: #108797

Error Message

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

{
  "ErrorMessage": "OpenQA.Selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Sample log:
https://helixre107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-runtime-refs-pull-108797-merge-b672a2c11f99427a9e/Microsoft.CSharp.Tests/1/console.618ae569.log?skoid=8eda00af-b5ec-4be9-b69b-0919a2338892&sktid=72f988bf-86f1-41af-91ab-2d7cd011db47&skt=2024-10-14T19%3A59%3A12Z&ske=2024-10-14T20%3A59%3A12Z&sks=b&skv=2024-05-04&sv=2024-05-04&st=2024-10-14T19%3A59%3A12Z&se=2024-10-14T20%3A59%3A12Z&sr=c&sp=r&sig=zPghjJW77UN3nV9xrZucrdLlqVHObIDrVvS37NXBv9k%3D

ChromeDriver was started successfully.
Connection refused [::ffff:127.0.0.1]:36887 (localhost:36887)
[15:11:06] warn: Failed to start the browser, attempt #0: OpenQA.Selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally.
                   (unknown error: DevToolsActivePort file doesn't exist)
                   (The process started from chrome location /datadisks/disk1/work/AC2B0958/p/chrome-linux/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
                    at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
                    at OpenQA.Selenium.Chromium.ChromiumDriver..ctor(ChromiumDriverService service, ChromiumOptions options, TimeSpan commandTimeout)
                    at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeDriverService service, ChromeOptions options, TimeSpan commandTimeout)

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=840205
Error message validated: [OpenQA.Selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/14/2024 8:05:32 PM UTC

Report

Summary

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

Activity

  1. ericstj
    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 Oct 14, 2024
  2. ghost added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Oct 14, 2024
  3. dotnet-policy-service
    added
    untriagedNew issue has not been triaged by the area owner
    on Oct 14, 2024
  4. carlossanlop
    added
    arch-wasmWebAssembly architecture
    os-browserBrowser variant of arch-wasm
    and removed
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Oct 14, 2024

  5. dotnet-policy-service commented on Oct 14, 2024

    @dotnet-policy-service
    dotnet-policy-servicebot
    on Oct 14, 2024 – with Dotnet Policy Service
    Contributor

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

  6. carlossanlop commented on Oct 14, 2024

    @carlossanlop
    carlossanlop
    on Oct 14, 2024
    Contributor

    This failure is heavily impacting the 6.0 PRs CI.

  7. jeffschwMSFT
    added
    area-VM-meta-mono
    on Oct 15, 2024
  8. lewing
    added this to the 10.0.0 milestone on Nov 4, 2024
  9. lewing
    assigned
    ilonatommy
    on Nov 4, 2024
  10. dotnet-policy-service
    removed
    untriagedNew issue has not been triaged by the area owner
    on Nov 4, 2024

  11. ilonatommy commented on Nov 5, 2024

    @ilonatommy
    ilonatommy
    on Nov 5, 2024
    Member

    The error can indicate a mismatch of chromedriver and chrome version. Failing tests are on Linux (we're not testing Windows at all). We are using chromedriver: 84.0.4147.0, chrome: Chromium 84.0.4147.0 there, so they are matching versions:

    runtime/src/libraries/sendtohelixhelp.proj

    Line 330 in 9623ff9

    <ChromiumRevision>768968</ChromiumRevision>

    The main difference between net6 and current main is missing --no-sandbox argument that was added to xharness in dotnet/xharness#951. It is reported as a fix for this exact error and it bypasses the OS's security model. I will backport the mentioned PR and see if this helps.

  12. ilonatommy
    removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Jan 14, 2025

  13. pavelsavara commented on Jul 18, 2025

    @pavelsavara
    pavelsavara
    on Jul 18, 2025
    Member

    I think this could be closed @ilonatommy ?

  14. ilonatommy
    closed this as completedon Jul 18, 2025
  15. github-actions
    locked and limited conversation to collaborators on Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Known Build ErrorUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architecturearea-VM-meta-monoos-browserBrowser variant of arch-wasm

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions