GPU tests on Linux run on SwiftShader instead of the real GPU
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- playwright, typescript
- Domain
- testing
Research direction
Start with the launchOptions.args in packages/runntime/vitest.config.ts and bench/vitest.config.ts, which currently pass only --enable-unsafe-webgpu. Run pnpm --filter runntime test:gpu on Linux and check navigator.gpu.requestAdapter(); it should report SwiftShader with shader-f16 missing. Done means that on Linux with a Vulkan driver the adapter is the real GPU with no skipped tests, while macOS and Windows keep their current args. Wait for a maintainer to confirm the Linux-only flag change before opening a PR.
Written by the indexing model from the issue text.
Description
Area
Core (engine, ops, kernels)
Description
On Linux, pnpm --filter runntime test:gpu does not run on the machine's GPU. Headless Chromium launched with only --enable-unsafe-webgpu (packages/runntime/vitest.config.ts) gets a SwiftShader adapter, the CPU fallback, which has no shader-f16. Nothing says so: the shader-f16 cases skip with their reason and the run looks like a normal one.
Same machine, same code (the branch of #120), 1849 tests:
| adapter | passed | skipped | failed | time |
|---|---|---|---|---|
| SwiftShader (current config) | 858 | 949 | 35 | 338 s |
| AMD GPU (with the flags below) | 1840 | 0 | 1 | 47 s |
On SwiftShader half the suite is skipped, and the 35 failures are timeouts, SwiftShader rounding and leak lists written for the f16 routes. #57 was found on the real GPU, where main fails 97 tests.
bench/vitest.config.ts has the same problem, so bench:ab on Linux measures SwiftShader.
The real GPU needs both --enable-features=Vulkan and --use-angle=vulkan. Either one alone still gives SwiftShader.
Steps to reproduce
- On Linux with a Vulkan driver, run
pnpm --filter runntime test:gpu. - 949 tests are skipped.
navigator.gpu.requestAdapter()in that browser reportsgoogle/swiftshader,shader-f16missing. - Add
'--enable-features=Vulkan', '--use-angle=vulkan'tolaunchOptions.argsand run again: the adapter is the GPU, withshader-f16, and nothing is skipped.
Proposed fix: add those two flags to both vitest configs only when process.platform === 'linux', so macOS and Windows keep their current setup. I don't know if the current config is meant to fall back to SwiftShader on Linux, so I'll wait for your confirmation: if this sounds right, let me know and I'll open the PR.
Platform
Browser (please name which one)
ruNNtime version
0.2.0 (main, 43053ee, plus #120)
Browser
Chromium 156.0.8078.4 (Playwright, headless)
Operating system
Arch Linux, kernel 7.2.2
GPU
AMD Radeon 610M (Mendocino, RDNA2, PCI 1002:1506), Mesa 26.2.1 RADV
WebGPU features
shader-f16, subgroups
AI model
No response
Console output and performance logs
Acknowledgements
Yes
- Dominant language
- TypeScript
- Stars
- 121
- Forks
- 7
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 48
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from software-mansion/runntime
-
core enhancement performance
Difficulty 5/5 Over a week Newbie friendliness 15/100
software-mansion/runntime#118 ·
Maintainers usually reply within 3 days
-
bug zoo
Difficulty 3/5 1-2 days Newbie friendliness 40/100
software-mansion/runntime#117 ·
Maintainers usually reply within 3 days
-
enhancement high priority
Difficulty 3/5 1-2 days Newbie friendliness 73/100
software-mansion/runntime#113 ·
Maintainers usually reply within 3 days
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
software-mansion/runntime#103 · 1 reaction ·
Maintainers usually reply within 3 days
-
kernels performance zoo
Difficulty 5/5 Over a week Newbie friendliness 35/100
software-mansion/runntime#87 ·
Maintainers usually reply within 3 days
All issues in software-mansion/runntime
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
nip98: validateEvent skips the payload check for a string or bytes bodyMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nbd-wtf/nostr-tools#599 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LemmyNet/lemmy-ui#4442 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Zettlr/Zettlr#6664 · 1 comment ·
Maintainers usually reply within 1 day
-
Microsoft Outlook add attachment reads the binary field from item 0Possibly taken @joshbarros claimed this today. Openstatus:in-linear
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
n8n-io/n8n#44021 · 2 comments ·
Maintainers usually reply within 1 day