-
-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
Update for CUDA 12.8.0 #33
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13016619362. Examine the logs at this URL for more detail. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2025.01.23.20.59.37
@conda-forge-admin, please restart ci |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2025.01.24.17.08.54
Seeing the following error on CI (also attached log for posterity)
Looks like Linux |
Was wondering why we don't see the same error on Linux libcublas-feedstock/recipe/meta.yaml Line 115 in 79f18e0
|
Should we be setting the c stdlib version in the CBC then? The file is pretty empty right now. |
We need to make several changes here. Unfortunately need to call it for the day. We will need to pick this up Monday |
Submitted fixes in PR: #34 These are against CUDA 12.6. Once those go in, we can make one line change to |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
@conda-forge-admin , please re-render |
…nda-forge-pinning 2025.01.28.04.06.09
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merged the aforementioned GLIBC fixes in PR: #34
Have merged in the latest from main
into this PR and resolved conflicts
Bumped Linux x86_64
's GLIBC version to 2.28 based on our observations above (please see comments below for details). Also re-rendered to propagate this info through
This should fix the test failure we saw before unblocking this PR
@@ -2,4 +2,4 @@ arm_variant_type: # [aarch64] | |||
- sbsa # [aarch64] | |||
c_stdlib_version: # [linux] | |||
- 2.28 # [linux and aarch64] | |||
- 2.17 # [linux and x86_64] | |||
- 2.28 # [linux and x86_64] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have set Linux x86_64
to use GLIBC 2.28 based on our observations above: #33 (comment)
@@ -5,7 +5,7 @@ c_compiler_version: | |||
c_stdlib: | |||
- sysroot | |||
c_stdlib_version: | |||
- '2.17' | |||
- '2.28' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can now see GLIBC 2.28 is used after a re-render
|
||
build: | ||
number: 1 | ||
number: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reset the build/number
as it was bumped in the previous PR
xref: conda-forge/cuda-feedstock#63