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

[gpuCI] Forward-merge branch-22.08 to branch-22.10 [skip gpuci] #11416

Merged
merged 1 commit into from
Aug 1, 2022

Conversation

GPUtester
Copy link
Collaborator

Forward-merge triggered by push to branch-22.08 that creates a PR to keep branch-22.10 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge.

… cudf recipe (#11412)

Arrow 8.0.1 just got built and uploaded to conda-forge and there's an associated PR to update the pinning to 8.0.1. Currently the recipes pin to 8.0.0 explicitly which will cause solving issues. Instead of just changing to 8.0.1, this PR relaxes the pinning to allow minor and patch versions to get pulled as there hasn't been any nvcc compiler issues in a while and Arrow strives to not introduce API / ABI breakages in minor and patch versions. Additionally, the cudf recipe seems to be unnecessarily setting requiring a cuda build of pyarrow which should no longer be needed after #10995.

Would really like this in for 21.08 if possible, but happy to change to just pin 8.0.1 if preferred.

Authors:
  - Keith Kraus (https://github.com/kkraus14)

Approvers:
  - AJ Schmidt (https://github.com/ajschmidt8)

URL: #11412
@GPUtester GPUtester requested a review from a team as a code owner August 1, 2022 16:00
@GPUtester GPUtester merged commit 8709e29 into branch-22.10 Aug 1, 2022
@GPUtester
Copy link
Collaborator Author

SUCCESS - forward-merge complete.

@github-actions github-actions bot added the conda label Aug 1, 2022
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.

None yet

2 participants