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

Update for CUDA 12.4.0 #37

Merged
merged 3 commits into from
Mar 6, 2024
Merged

Conversation

adibbley
Copy link
Contributor

@adibbley adibbley commented Mar 5, 2024

@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.

@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

@jakirkham jakirkham marked this pull request as ready for review March 6, 2024 10:41
@jakirkham jakirkham requested a review from a team as a code owner March 6, 2024 10:41
@jakirkham jakirkham added the automerge Merge the PR when CI passes label Mar 6, 2024
Copy link
Contributor

github-actions bot commented Mar 6, 2024

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

I considered the following status checks when analyzing this PR:

  • linter: passed
  • travis: passed
  • azure: passed

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

@jakirkham jakirkham removed the automerge Merge the PR when CI passes label Mar 6, 2024
@jakirkham
Copy link
Member

Same issue as seen in this thread: conda-forge/nvidia-gds-feedstock#5 (comment)

Please read subsequent comments in that thread for more details

@adibbley adibbley added the automerge Merge the PR when CI passes label Mar 6, 2024
@adibbley
Copy link
Contributor Author

adibbley commented Mar 6, 2024

@conda-forge-admin, please restart ci

@github-actions github-actions bot merged commit 2e1b741 into conda-forge:main Mar 6, 2024
7 checks passed
@jakirkham
Copy link
Member

As Alex pointed out to me offline, Travis CI did not run on main

This appears to be due to the fact that Travis CI is rejecting build requests. Raised this issue with Travis CI recently and have included this case as another example in that thread

Travis CI requests: Screenshot 2024-03-06 at 11 34 26 AM

Have manually started a new Travis CI build to fix this issue

Also this build has since passed. So no further action from maintainers needed

@jakirkham
Copy link
Member

Just for future reference, am writing down the steps needed to start a new Travis CI build on main

For the next steps to work, please make sure to sign in to Travis CI. This can be done just with a GitHub login. If this is your first time, there may be a couple pages to go through to configure permissions and complete the login process

Start by going to the "Current build status" section in the README and click the Travis badge there

Current build status: Screenshot 2024-03-06 at 11 47 00 AM

Next find the menu on the right side of the screen called "More options" and select "Trigger build"

More options: Screenshot 2024-03-06 at 11 37 43 AM

This opens a dialog box. There are more options we can use here. Though to simply start a build on main, we can use the defaults and click the button "Trigger custom build" on the bottom

Triggering build: Screenshot 2024-03-06 at 11 37 52 AM

This should start a fresh build on main. Can go to "Current" or "Build history" tabs to find it

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.

2 participants