Skip to content

Run WebGPU tests on self-hosted CI - #9406

Open
davepagurek wants to merge 14 commits into
processing:mainfrom
davepagurek:webgpu-ci
Open

davepagurek wants to merge 14 commits into
processing:mainfrom
davepagurek:webgpu-ci

Conversation

@davepagurek

Copy link
Copy Markdown
Contributor

So currently we don't run the WebGPU tests on CI when contributors make changes. This currently means I have to manually clone people's changes and run them myself to confirm, so WebGPU changes are especially painful to review.

The problem is that while Chrome's SwiftShader-based CPU fallback works on CI for WebGL, there isn't an equivalent for WebGPU, and GitHub's free Actions runners do not have a real GPU attached.

A possible workaround that's "free" (ish) is to use self-hosted runners. I've got a server in my closet that I can run this on. The idea is that:

  • You generate a Personal Access Token that lets you pick up + run test jobs
  • An orchestrator runs in the background polling periodically for jobs to run
  • Each job gets run in a fresh docker container so past runs don't affect future runs
  • Jobs are run behind a network proxy to prevent them from accessing anything they shouldn't

I've tested this over on my fork of p5 here davepagurek#2 and using this project to manage the orchestrator/job runner: https://github.com/davepagurek/p5-ci-runner/

The required changes in the p5 repo were:

  • A flag to make sure we WebGL fallback doesn't run for tests (we want to make sure we're testing WebGPU!)
  • A ci job that runs on self-hosted runners only, using a virtual screen to make sure GPU stuff works properly
  • some vitest config updates to make sure it uses an actual gpu for webgpu tests

Before merging this I need to get a personal access token for the real p5 repo, not my fork, and attach my server, and then we should see tests run here.

@p5-bot

p5-bot Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant