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

Refresh CUDA-Python 11.8 #79

Merged
merged 10 commits into from
May 2, 2024

Conversation

jakirkham
Copy link
Member

@jakirkham jakirkham commented May 1, 2024


Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • In conda-forge.yml: $.bot = {'abi_migration_branches': [11.8]}.

    {'abi_migration_branches': [11.8]} is not valid under any of the given schemas

    Schema
    {
      "anyOf": [
        {
          "$ref": "#/$defs/BotConfig"
        },
        {
          "type": "null"
        }
      ]
    }

For recipe:

@conda-forge-webservices
Copy link
Contributor

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) and found it was in an excellent condition.

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

For recipe:

@conda-forge-webservices
Copy link
Contributor

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) and found it was in an excellent condition.

As GitHub archives are generated on-demand and the process of that
generation can be changed between runs, it is possible to get a
different checksum each time. It appears the checksum changed recently.
So refresh it.
@jakirkham jakirkham marked this pull request as ready for review May 1, 2024 22:10
@jakirkham jakirkham added automerge Merge the PR when CI passes and removed automerge Merge the PR when CI passes labels May 1, 2024
@jakirkham jakirkham added automerge Merge the PR when CI passes and removed automerge Merge the PR when CI passes labels May 1, 2024
The Azure `linux_aarch64` builds are running out-of-memory. So to fix
that enable a swapfile on Azure.
@jakirkham jakirkham added the automerge Merge the PR when CI passes label May 1, 2024
@github-actions github-actions bot merged commit f187213 into conda-forge:11.8 May 2, 2024
22 checks passed
Copy link
Contributor

github-actions bot commented May 2, 2024

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed

Thus the PR was passing and merged! Have a great day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge the PR when CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant