Add an on-demand CUDA execution job and make it a release prerequisite
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with ci.yml, release.yml, and step 0 of docs/RELEASING.md; inspect the existing CUDA test commands and the STATUS.md matrix. Define a GPU runner workflow that can be dispatched and called by the release workflow, runs the listed CUDA suites, uploads logs, and records the driver, GPU, and SHA. Done means it has passed on a main SHA and blocks tagged releases without a green run or documented override.
Written by the indexing model from the issue text.
Description
Today — no CI job executes CUDA code. ci.yml runs on ubuntu-latest (11 jobs) and macos-latest (the metal job); CUDA is make check-cuda / lint-cuda only (ci.yml:92-94,166-168). The GPU tests are #[ignore]d (crates/oxidelake-device/src/cuda/mod.rs:524,553,649; crates/oxidelake-compute/tests/conformance.rs:317). The only CUDA execution on record is the manual T4 session of 2026-09-06, which found a correctness bug that 3 seeds × 5 sizes of CPU conformance had not (STATUS.md). Since then nothing re-executes CUDA; every kernel or ops.rs change can regress silently. docs/RELEASING.md step 0 requires the stress workflow and nothing GPU-side; make test-termlens-cli is not in the checklist either.
Why it is worth fixing — STATUS's own lesson: "compiles with --features cuda is not a verification status". A production release without a CUDA run on the release candidate re-creates the gap the T4 session closed once.
Fix — a gpu.yml with workflow_dispatch (and workflow_call from release.yml as a required job) that runs on a self-hosted or ephemeral cloud GPU runner: OXIDE_BACKEND=cuda cargo test -p oxidelake-device --features cuda -- --include-ignored, the compute conformance suite, and crates/oxidelake-runtime/tests/embedded.rs under --target cuda; uploads the log as an artifact; appends a dated row (driver, GPU, SHA) to STATUS.md's matrix by PR. Add it and make test-termlens-cli to RELEASING.md step 0.
Done when — the workflow exists and has run green at least once on a CUDA machine for a main SHA; release.yml refuses to publish without a green gpu run for the tagged SHA (or the maintainer's documented override).
- Dominant language
- Rust
- Stars
- 1
- Forks
- 2
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 vyncint/oxidelake
-
dependencies documentation
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
Prepare the Ballista 55 / DataFusion 55 / arrow 59 chain bump ahead of the release that fixes thriftOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 32/100
vyncint/oxidelake#40 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in vyncint/oxidelake
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
yunfie-twitter/Palleria#474 ·
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
servo/rust-smallvec#827 ·
Maintainers usually reply within 1 day
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day