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

Forward-merge branch-24.06 into branch-24.08 #313

Closed
wants to merge 5 commits into from

Conversation

rapids-bot[bot]
Copy link

@rapids-bot rapids-bot bot commented May 24, 2024

Forward-merge triggered by push to branch-24.06 that creates a PR to keep branch-24.08 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. See forward-merger docs for more info.

trxcllnt and others added 5 commits May 22, 2024 13:08
)

* Add feature to build openmpi from source with CUDA and UCX support
* add ucx + openmpi images to matrix.yml
Co-authored-by: github-actions <github-actions@github.com>
* add release-all.yml workflow to release on push to branch-* and release tags
* support only building a subset of images when pushing, and optionally when building manually
* rename release.yaml to release-linux.yml
* Use new UCX images in devcontainers, add CUDA 12.4 devcontainers, test CUDA 11.8, 12.0, 12.2, and 12.4 in CI

* set git-lfs feature's autoPull arg to false

* remove 12.4 devcontainers and revert to building CUDA 12.0 and 12.2 in CI

* always add origin and upstream remotes

* support defining envvars in manifest.yaml for cpp libs

* build multiple archs in parallel in CI

* temporarily use my rapids-cmake fork with a fix for nvtx3

* build up to 6 archs at a time

* bump up raft device obj memory usage

* default max_archs to the inferred n_arch

* default to compiling RAFT, set MAX_DEVICE_OBJ_MEMORY_USAGE=3 for cuvs

* use rapids-cmake branch-24.06 again

* fix divide by zero
Copy link
Author

rapids-bot bot commented May 24, 2024

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

@trxcllnt trxcllnt closed this May 25, 2024
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.

1 participant