-
Notifications
You must be signed in to change notification settings - Fork 66
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] Compute Sanitizer reports errors for the TableTest#testORCReadAndWriteForDecimal128
test
#1338
Comments
|
TableTest#testORCReadAndWriteForDecimal128
fails when running with Compute SanitizerTableTest#testORCReadAndWriteForDecimal128
test
I reproduced the issue. https://github.com/rapidsai/cudf/blob/v23.08.00/cpp/src/io/orc/dict_enc.cu#L68-L70
grid_size.y is 0 when I print it out. This means the @jlowe Help confirm. It's a cuDF bug, I'll post an issue. |
If I update
==>>
|
Yes, I believe the dimensions are supposed to be greater than zero. If this is an illegal launch configuration, why do we only see a CUDA error when running under the sanitizer? I would expect the driver to return an error when trying to launch a kernel with an invalid launch config. Or does it treat it as a no-op instead? |
Depends on cuDF issue: rapidsai/cudf#13887 |
Seem cuDf has fixed the issue, @res-life can you verify again. |
cuDF PR: rapidsai/cudf#14897 |
Retarget this issue to 24.04, because the cuDF branch 24.02 is locked. |
This test is excluded temporarily in PR rapidsai/cudf#13872.
Error stack from the Compute Sanitizer.
Repro steps:
1 Apply the two PRs, rapidsai/cudf#13872 and #1321
2 Remove the
noSanitizer
tag from this test. And run./build/build-in-docker test -Dtest=TableTest -DUSE_SANITIZER=ON
.The text was updated successfully, but these errors were encountered: