| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
TF_BUILD_CUDA is off in every job, since the runners have no GPU, so the cudaGraph tests never run. PantheonSim simulates a GPU on the runner's CPU; this job builds the CUDA unit tests and runs them there.
| Back | FazBrowse Home | New Git URL |
Every job builds with TF_BUILD_CUDA off, because the runners have no GPU, so the cudaGraph unit tests (unittests/cuda) never run in CI. This adds one job to ubuntu.yml that builds them and runs them on a simulated NVIDIA T4.
How: PantheonSim, via pantheongpu/setup-pantheonsim, simulates the GPU on the runner's CPU. The kernels run from their PTX and the CUDA Graph calls go through the simulator's runtime, so the results are real. There is no timing model, so this checks correctness, not performance.
Changes: one new job, cuda-test-simulated-gpu, in the same style as the others:
Nothing else changes.
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:
Disclosure: I maintain PantheonSim. Running these tests found a gap in it that's now fixed: a graph's memset node on cudaMallocManaged memory. If the job is ever flaky or wrong, please open an issue at pantheongpu/pantheonsim and I'll fix it on our side.