fix(compute): nine GPU tests panicked without an adapter — the nightly coverage run was RED six days on an environment fact (PMAT-1106) - #3116
Conversation
…er (coverage nightly) Pmat-Ticket: PMAT-1106 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…he nightly coverage run was RED for six days on an environment fact
backends::gpu::device::backward::tests called GpuDevice::new().expect("GPU device") nine times. Under cargo llvm-cov on yoga-build2 (a docker runner with no GPU passthrough) the two silu_backward tests panicked and the whole coverage run exited 2 (run 34575134766); the same class in aprender-cgp is #2848. A missing adapter is an environment fact, not a kernel defect: device_or_skip() prints 'SKIP: no GPU adapter on this host (<err>)' and the test returns. Proven both ways on lambda-vector: with VK_ICD_FILENAMES pointed at nothing, 9 SKIP lines and 9 passed in 0.00 s; with the real adapter, 0 SKIP lines and 9 passed in 1.42 s. The box that has an adapter stays the gate.
Pmat-Ticket: PMAT-1106
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
§13.11 rung 1 — quorum shadow verdict Shadow mode: this records a verdict and merges nothing. A refusal |
…r runs aprender-compute's gpu tests on intel, where there is no adapter; roadmap: PMAT-1106 entry appended Pmat-Ticket: PMAT-1102 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Falsifier ran (2026-09-11 10:19Z, |
…ries + PMAT-1106 kept Pmat-Ticket: PMAT-1106 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Superseded: this branch's commits (device_or_skip for the wgpu device tests) are already merged into #3112 (PMAT-1102), which also carries the aarch64 lint fixes and two dark-test fixes surfaced by the quick tier. Cancelled this PR's rerun to free X64 runner slots for #3112 (the queue was 17 deep at 15:04Z); will close this PR once #3112 lands. — Claude, autonomous fleet loop |
What
backends::gpu::device::backward::testscalledGpuDevice::new().expect("GPU device")nine times. Undercargo llvm-covon yoga-build2 (docker runner, no GPU passthrough) two of them panicked and the whole nightly coverage run exited 2 — run 34575134766, and the run is RED six days running (the other half of that redness is the same class in aprender-cgp, #2848, pulled into 0.67.0).A missing adapter is an environment fact, not a kernel defect.
device_or_skip()printsSKIP: no GPU adapter on this host (<err>)and the test returns; the box that has an adapter stays the gate.Proven both ways (lambda-vector,
cargo test -p aprender-compute --lib --features gpu -- backends::gpu::device::backward --nocapture)VK_ICD_FILENAMES=/nonexistent(no adapter)SKIP:lines, 9 passed in 0.00 sSKIP:lines, 9 passed in 1.42 scargo fmt --check;cargo clippy -p aprender-compute --all-targets -- -D warnings -A unused-variables(CI's chain, default features)cargo clippy -p aprender-compute --lib --tests --features gpu -- -D warningslen() == 0atbackends/gpu/pool.rs:169, a gpu-feature-only test target no gate lints today (same class as the aprender-gpu dark targets noted in memory)Falsifier of record: the next
coverage-nightly.ymlrun (03:00 UTC) — with this and #2848 on main it must reach the report step and print a line-coverage figure instead of exiting 2 incargo test.Refs PMAT-1106, #2848, operator rule 2026-09-11 ("nightly we should have a low priority code coverage run with goal of eventually getting to 95% coverage").
🤖 Generated with Claude Code