Skip to content

Use CTK 12.9.1 for cuda-bindings 12.9.x #955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leofang merged 8 commits into from
Sep 11, 2025
Merged

Use CTK 12.9.1 for cuda-bindings 12.9.x #955

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
6d031d9
bump all CI jobs to CUDA 12.9.1
kkraus14 Sep 9, 2025
3f0b4b2
CI: Consolidate test matrix configurations into ci/test-matrix.json w…
Copilot Sep 5, 2025
8edaa4d
forgot to add windows
kkraus14 Sep 10, 2025
2b6d3ea
rerun codegen with 12.9.1 and update result/error explanations
kkraus14 Sep 10, 2025
c3cef70
First stab at the filter for CUDA < 13 in CI
cryos Sep 10, 2025
1510ff8
Get data from the top-level array
cryos Sep 10, 2025
18498da
Use the map function on select output
cryos Sep 10, 2025
90b37d5
CI: Move to self-hosted Windows GPU runners
cryos Sep 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,7 @@ jobs:
build-type: pull-request
host-platform: ${{ matrix.host-platform }}
build-ctk-ver: ${{ needs.ci-vars.outputs.CUDA_BUILD_VER }}
matrix_filter: "select(([.CUDA_VER // empty | split(\".\")[] | tonumber] as $v | ($v[0] < 13)))"

@kkraus14 kkraus14 Sep 10, 2025

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: can we programmatically derive 13 here and so we can have this unified across main and 12.9.x and allow it to nicely carry over to the future where we have main and 13.x.y?

@cryos cryos Sep 10, 2025

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You want to derive the CUDA major version from the branch name? I see the motivation, just thinking through what we want to key from programatically.

@kkraus14 kkraus14 Sep 10, 2025

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or from the version json file since it would always be aligned to the major version we want to use? It's not a big deal though where if we want to punt to a future PR that's totally fine.

@cryos cryos Sep 10, 2025 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Third time was the charm 🎉 I can look at it for a follow up, it shouldn't be much, but it would be good to get this merged now. Lots of meetings today sadly...


test-windows:
strategy:
Expand All @@ -90,6 +91,7 @@ jobs:
build-type: pull-request
host-platform: ${{ matrix.host-platform }}
build-ctk-ver: ${{ needs.ci-vars.outputs.CUDA_BUILD_VER }}
matrix_filter: "select(([.CUDA_VER // empty | split(\".\")[] | tonumber] as $v | ($v[0] < 13)))"

# doc:
# name: Docs
Expand Down
Loading