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

[BUG] Unit test suite fails with Null data pointer in GpuTimeZoneDB #10129

Closed
NVnavkumar opened this issue Dec 29, 2023 · 1 comment · Fixed by NVIDIA/spark-rapids-jni#1670
Closed
Assignees
Labels
bug Something isn't working

Comments

@NVnavkumar
Copy link
Collaborator

NVnavkumar commented Dec 29, 2023

Describe the bug

From premerge failure in #10100, replicated locally:

When running the full suite of unit tests (not specific unit test Suites), tests will fail with an error in GpuTimeZoneDB:

2023-12-29T18:33:47.2798932Z [2023-12-29T18:12:35.013Z] �[32mTimeZoneSuite:�[0m
2023-12-29T18:33:47.2799368Z [2023-12-29T18:12:35.278Z] �[31m- test timestamp to utc timestamp *** FAILED ***�[0m
2023-12-29T18:33:47.2800726Z [2023-12-29T18:12:35.280Z] �[31m  ai.rapids.cudf.CudfException: CUDF failure at: /home/jenkins/agent/workspace/jenkins-spark-rapids-jni_nightly-dev-632-cuda11/thirdparty/cudf/cpp/src/column/column_view.cpp:56: Null data pointer.�[0m
2023-12-29T18:33:47.2801283Z [2023-12-29T18:12:35.280Z] �[31m  at ai.rapids.cudf.ColumnView.makeCudfColumnView(Native Method)�[0m
2023-12-29T18:33:47.2801965Z [2023-12-29T18:12:35.280Z] �[31m  at ai.rapids.cudf.ColumnView$NestedColumnVector.createViewHandle(ColumnView.java:4940)�[0m
2023-12-29T18:33:47.2802661Z [2023-12-29T18:12:35.280Z] �[31m  at ai.rapids.cudf.ColumnView$NestedColumnVector.createViewHandle(ColumnView.java:4932)�[0m
2023-12-29T18:33:47.2803407Z [2023-12-29T18:12:35.280Z] �[31m  at ai.rapids.cudf.ColumnView$NestedColumnVector.createColumnVector(ColumnView.java:4892)�[0m
2023-12-29T18:33:47.2804030Z [2023-12-29T18:12:35.280Z] �[31m  at ai.rapids.cudf.HostColumnVector.copyToDevice(HostColumnVector.java:263)�[0m
2023-12-29T18:33:47.2804767Z [2023-12-29T18:12:35.280Z] �[31m  at com.nvidia.spark.rapids.jni.GpuTimeZoneDB.getFixedTransitions(GpuTimeZoneDB.java:290)�[0m
2023-12-29T18:33:47.2805458Z [2023-12-29T18:12:35.280Z] �[31m  at com.nvidia.spark.rapids.jni.GpuTimeZoneDB.getTransitions(GpuTimeZoneDB.java:283)�[0m
2023-12-29T18:33:47.2806253Z [2023-12-29T18:12:35.280Z] �[31m  at com.nvidia.spark.rapids.jni.GpuTimeZoneDB.fromTimestampToUtcTimestamp(GpuTimeZoneDB.java:107)�[0m
2023-12-29T18:33:47.2807131Z [2023-12-29T18:12:35.280Z] �[31m  at com.nvidia.spark.rapids.timezone.TimeZoneSuite.$anonfun$testFromTimestampToUtcTimestamp$2(TimeZoneSuite.scala:223)�[0m
2023-12-29T18:33:47.2808109Z [2023-12-29T18:12:35.280Z] �[31m  at com.nvidia.spark.rapids.timezone.TimeZoneSuite.$anonfun$testFromTimestampToUtcTimestamp$2$adapted(TimeZoneSuite.scala:219)�[0m
2023-12-29T18:33:47.2808316Z [2023-12-29T18:12:35.280Z] �[31m  ...�[0m

Steps/Code to reproduce bug
Run the full unit test suite using mvn package or mvn verify without specifying -DwildcardSuites

@NVnavkumar
Copy link
Collaborator Author

This has only manifested in the to_date PR, but is actually a general bug with GpuTimeZoneDB. Turns out the class is not idempotent, will push a fix in spark-rapids-jni.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants