-
Notifications
You must be signed in to change notification settings - Fork 31
Add rapidsmpf to manifest #497
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
base: branch-25.06
Are you sure you want to change the base?
Conversation
I guess this also needs the bind mounts... |
cc @trxcllnt |
@wence- are the |
I had rapidsai/rapidsmpf#233 in flight which it probably didn't pick up |
That is now in, but I don't have the powers to restart the builds |
@wence- I've re-run CI a few times now, still seems to be failing with this error. Is the pip container missing any dependencies, or using an incompatible gcc version? Should we add a devcontainers job to Click to expand cpp/tests/test_shuffler.cpp error
|
Ah let me check, this is probably because the pip containers use g++11 (conda uses g++13). Yes, would be good to add an individual run for rapidsmpf. I will also submit a fix for this issue. |
Yeah, this is a gcc 11 bug (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79501 and https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100983) which I will work around |
@trxcllnt the gcc 11 WAR is now merged. But as Peter notes, we don't want to build for cuda 11.8. Is there a way in the manifest to conditionally remove rapidsmpf for the cuda 11.8 part of the matrix. Or is it sufficient that the 11.8 devcontainer.json files now don't mention rapidsmpf? |
That just ensures the source isn't mounted from the host... the
There is not, because we haven't encountered this before. We don't test 11.8 in CI, so this would only affect someone using the 11.8 combined devcontainer. That's (probably?) an uncommon use-case, and given that we're about to drop 11.8 across the board, I'd say it's fine to leave it. If someone is using the combined 11.8 devcontainer and re-runs |
For context, that is exactly why we dropped CUDA 11 support in RAPIDSMPF, we were planning to release it only around the time when CUDA 11 would be dropped and thus there was no point in even dealing with it. |
Something different about the |
Looks like some dependencies aren't included when generating |
No description provided.