-
Notifications
You must be signed in to change notification settings - Fork 235
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
Fix String tests on Databricks 14.3 #11535
Comments
mythrocks
added a commit
to mythrocks/spark-rapids
that referenced
this issue
Oct 28, 2024
Fixes NVIDIA#11535. This commit fixes the failure of `test_startswith` and `test_endswith` in `string_test.py` on Databricks 14.3. This is, in effect, a follow-on to the changes introduced in NVIDIA#11247, where `test_endswith` was skipped for Databricks 4.0, on account of https://issues.apache.org/jira/browse/SPARK-48995. It appears that that bug afflicts Databricks 14.3 as well. This commit handles both `test_startswith` and `test_endswith` for Databricks 14.3 and Apache Spark 4.0. Signed-off-by: MithunR <[email protected]>
This failure should be addressed by #11669. |
mythrocks
added a commit
that referenced
this issue
Nov 6, 2024
* Fix string_test for [databricks] 14.3 Fixes #11535. This commit fixes the failure of `test_startswith` and `test_endswith` in `string_test.py` on Databricks 14.3. This is, in effect, a follow-on to the changes introduced in #11247, where `test_endswith` was skipped for Databricks 4.0, on account of https://issues.apache.org/jira/browse/SPARK-48995. It appears that that bug afflicts Databricks 14.3 as well. This commit handles both `test_startswith` and `test_endswith` for Databricks 14.3 and Apache Spark 4.0. Signed-off-by: MithunR <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build the plugin against the Databricks 14.3 cluster using #11467. Once built successfully run the String tests by
TESTS=string_test.py jenkins/databricks/test.sh
The following tests fail
The text was updated successfully, but these errors were encountered: