Conversation
The Linux jobs exclude cust from cargo test because its tests need an NVIDIA GPU. PantheonSim simulates one on the runner's CPU; this job runs cust's unit and doc tests there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Linux CI runs
cargo test --workspace --exclude blastoff --exclude cudnn --exclude cust, because cust's tests need an NVIDIA GPU. This adds a job that runs them on a simulated one:cargo test -p cust, unit tests and doc tests.How: PantheonSim, via
pantheongpu/setup-pantheonsim, installs the CUDA toolkit and puts a simulated GPU behindlibcudaon the runner's CPU. cust's calls go through the simulator's driver API (contexts, streams, events, device and unified memory, CUDA arrays, modules, launches), so the results are real. There is no timing model, so this checks correctness, not performance.Changes: one new job at the end of
ci_linux.yml,test-cust-simulated-gpu, on a plainubuntu-24.04runner rather than the build containers:libclang-devfor bindgen;cargo test -p cust, withCUDA_PATHpointing at the toolkit.It uses the repo's pinned nightly from
rust-toolchain.toml. The existing jobs are unchanged.What it can touch: the action is pinned by commit (v0.1.2), not by a tag, and it pins the simulator it builds by commit too, so nothing in the job changes until you move the pin. The new job's token is read-only (
permissions: contents: read), and the action uses no token or secrets; it installs packages only from Ubuntu's and NVIDIA's repositories. The job isn't a required check, so a red run never blocks a merge unless you decide it should.What it gives, from a run on my fork:
ignored in the source), in about 5 seconds.Disclosure: I maintain PantheonSim. Running cust's tests found several gaps in its driver API that are now fixed: CUDA arrays,
cuMemcpy2D/3D, pitched and stream-ordered allocation,cuModuleGetGlobal, the context cache and shared-memory configuration, stream callbacks, andcuEventElapsedTime's refusals. If the job is ever flaky or wrong, please open an issue at pantheongpu/pantheonsim and I'll fix it on our side.🤖 Generated with Claude Code