-
Notifications
You must be signed in to change notification settings - Fork 902
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
[BUG] gpuCI is not building cuDF with PER_THREAD_DEFAULT_STREAM #9165
Comments
This issue has been labeled |
This issue has been labeled |
I suspect that this is due to the fact that we use conda builds and we don't specify Assuming that this is the problem, I'm not sure of the best fix. Can I just change |
I'm going to close this issue. #11281 has a lot of the salient discussion. libcudf is unlikely to ever provide both PTDS and non-PTDS builds simultaneously due to resource constraints. Our plan for stream safety has evolved (see especially #11943) and we are tracking progress towards exposing stream-ordered APIs in #13744. Ultimately the plan is to convert all testing to pass streams through as discussed in that issue. Once that is done we can add suitable multi-stream testing as needed without relying on compilation with PTDS. |
Describe the bug
#5673 enabled building with PER_THREAD_DEFAULT_STREAM for all gpuCI test builds of libcudf. This seems to have stopped working. This log of a recent PR build shows that the strings
PER_THREAD_DEFAULT_STREAM
andptds
do not appear in any of the compiler command lines.We had a pretty bad RMM bug that would have been caught if PTDS was still being tested.
I'm not sure why this is happening, as the
build.sh
scripts in cuDF are still passing the-ptds
option.Steps/Code to reproduce bug
Look at recent gpuCI libcudf compilation.
Expected behavior
PTDS should be enabled for libcudf test builds.
Environment overview (please complete the following information)
The text was updated successfully, but these errors were encountered: