Skip to content

CompatHelper: bump compat for CUDA in [weakdeps] to 6, (keep existing compat)#196

Open
github-actions[bot] wants to merge 1 commit into
masterfrom
compathelper/new_version/2026-04-11-00-20-34-283-01904402483
Open

CompatHelper: bump compat for CUDA in [weakdeps] to 6, (keep existing compat)#196
github-actions[bot] wants to merge 1 commit into
masterfrom
compathelper/new_version/2026-04-11-00-20-34-283-01904402483

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented Apr 11, 2026 •
edited by mcabbott
Loading

This pull request changes the compat entry for the CUDA package from 4, 5 to 4, 5, 6.
This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass before you merge this pull request.

Edit:
Closes #197 as a duplicate.

@mcabbott
Copy link
Copy Markdown
Owner

mcabbott commented Apr 11, 2026

https://github.com/JuliaGPU/CUDA.jl/releases/tag/v6.0.0

Many warnings like this on CI, plus failures which I don't think are new:

<head></head>
┌ Warning: CUDA runtime library `libcublasLt.so.13` was loaded from a system path, `/usr/local/cuda/lib64/libcublasLt.so.13`.
--
│ This may cause errors.
│
│ If you're running under a profiler, this situation is expected. Otherwise,
│ ensure that your library path environment variable (e.g., `PATH` on Windows
│ or `LD_LIBRARY_PATH` on Linux) does not include CUDA library paths.
│
│ In any other case, please file an issue.
└ @ CUDA ~/.julia/packages/CUDA/Il00B/src/initialization.jl:198

@ExpandingMan
Copy link
Copy Markdown

ExpandingMan commented Apr 16, 2026

I'm seeing heisenbug-like behavior on test failures on gradients when running locally. When I run test Tullio I get errors like can be seen in buildkite, but whenever I try pulling out the code to isolate it in a file and start hacking on it, the errors go away. I suspect it has something to do with Tracker. Since Tracker seems unmaintained I wonder if it's a good idea to continue to use that as a reference? Maybe swap it out for mooncake?

I don't get any warnings running locally.

@mateuszbaran mateuszbaran mentioned this pull request May 7, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mcabbott @ExpandingMan