Skip to content
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

Use global pinnings in build matrix (same elements as before) #114

Merged
merged 4 commits into from
Dec 6, 2024

Conversation

conda-forge-admin
Copy link
Contributor

@conda-forge-admin conda-forge-admin commented Dec 6, 2024

Cleans up how the build matrix is configured to leverage the global pinnings by doing the following...

  • Drop duplicated CUDA content from conda_build_config.yaml
  • Update skip to select out nvcc & re-render correctly
  • Re-render to pull in global pinnings and update variants for new Docker image scheme and CDTs

Packages are unchanged. So build/number stays the same

Fixes #113

@conda-forge-admin
Copy link
Contributor Author

conda-forge-admin commented Dec 6, 2024

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 (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12193730264. Examine the logs at this URL for more detail.

@conda-forge-admin conda-forge-admin marked this pull request as ready for review December 6, 2024 05:38
Drop the bulk of `conda_build_config.yaml` in favor of using the values
in the global pinnings. This cuts down on duplication of this content
and thus makes it easier to pull in the latest changes (like recent
Docker image and CDT changes).

Also adapt the recipe slightly so that we only pick out the `nvcc`
configuration. Plus make sure conda-smithy recognizes this is a CUDA
using recipe even though it does not use `compiler("cuda")` in the
build. Do this by adapting the `skip` to check `compiler("cuda")`
matches `nvcc*`.
@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

@jakirkham jakirkham changed the title MNT: rerender Use global pinnings in build matrix (same elements as before) Dec 6, 2024
@jakirkham jakirkham merged commit a6e2e0e into conda-forge:main Dec 6, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rework or drop conda_build_config.yaml
2 participants