Conversation
ccpp.yml builds GPUJPEG on runners with no GPU, so nothing that encodes or decodes runs in CI. A new workflow runs the unit tests and the regression suite on a simulated NVIDIA T4 (PantheonSim, via setup-pantheonsim), on pushes and pull requests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
ccpp.ymlbuilds GPUJPEG on GitHub's runners, which have no GPU, so nothing that encodes or decodes runs in CI. This adds a workflow that runs the unit tests and the regression suite on a simulated NVIDIA T4, on pushes todevelandmasterand on pull requests.How: PantheonSim, via
pantheongpu/setup-pantheonsim, simulates the GPU on the runner's CPU. The kernels run from their PTX (CMAKE_CUDA_ARCHITECTURES=75embeds it), so the results are real. There is no timing model, so this checks correctness, not performance.Changes: one new workflow,
.github/workflows/simulated-gpu.yml, onubuntu-24.04:CMAKE_CUDA_ARCHITECTURES=75and the shared CUDA runtime;ctest -R 'unittests|regression'undervgpu run, which puts the simulated GPU's libraries in place for the tests only. The build links against the toolkit's ownlibcudart, becauselibgpujpegreferences the OpenGL interop calls even when OpenGL is off.ccpp.ymlis unchanged.What it can touch: the action is pinned by commit (v0.1.1), 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 workflow'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:
unittestsandregressionboth pass; the tests take under a minute.Disclosure: I maintain PantheonSim. Running GPUJPEG's tests found three gaps in its CUDA runtime that are now fixed: copy directions, symbol copies from device memory, and the cache-preference calls. 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