Skip to content

Cannot run WebGPU tests on Chrome because of "--use-gl=swiftshader" #27994

Open

Description

@juj

I find that if I run Emscripten tests in Chrome, all the WebGPU tests

browser.test_webgpu_required_limits
browser.test_webgpu_basic_rendering_pthreads
browser.test_webgpu_basic_rendering_main_module
browser.test_webgpu_basic_rendering
browser.test_webgpu_basic_rendering_closure
browser.test_webgpu_basic_rendering_closure_advanced

fail, because no WebGPU contexts are available.

This issue goes away if I remove --use-gl=swiftshader from ChromeConfig in browser_common.py.

Any thoughts of why that flag is present there? Are WebGPU tests skipped on CircleCI? Could we remove --use-gl=swiftshader or put it behind a separate CircleCI-specific EMTEST_BROWSER_ARGS=... env. var that would be injected to browser launch?

Activity

  1. juj commented on Oct 16, 2026

    @juj
    CollaboratorAuthor

    Looks like there's

    EMTEST_LACKS_WEBGPU: "1"

    so WebGPU tests are skipped.

  2. sbc100 commented on Oct 16, 2026

    @sbc100
    Collaborator

    Maybe --use-gl=swiftshader is only needed for running tests headless? Perhaps it that flag could be moved from default_flags to headless_flags?

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions