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

Fix Collections tests on Databricks 14.3 #11532

Closed
razajafri opened this issue Sep 27, 2024 · 0 comments · Fixed by #11623
Closed

Fix Collections tests on Databricks 14.3 #11532

razajafri opened this issue Sep 27, 2024 · 0 comments · Fixed by #11623
Assignees
Labels
task Work required that improves the product but is not user facing

Comments

@razajafri
Copy link
Collaborator

Build the plugin against the Databricks 14.3 cluster using #11467. Once built successfully run the collection ops tests by TESTS=collection_ops_test.py jenkins/databricks/test.sh

The following tests fail

[gw3] [ 13%] FAILED ../../src/main/python/collection_ops_test.py::test_sequence_too_long_sequence
@razajafri razajafri assigned razajafri and unassigned razajafri Oct 3, 2024
@mythrocks mythrocks self-assigned this Oct 8, 2024
mythrocks added a commit to mythrocks/spark-rapids that referenced this issue Oct 17, 2024
Fixes NVIDIA#11532.

This commit introduces a RapidsErrorUtils shim for Databricks 14.3, to
deal with the new error messages thrown for large array/sequences.

This should fix the failure in `collection_ops_test.py::test_sequence_too_long_sequence`
on Databricks 14.3.
mythrocks added a commit to mythrocks/spark-rapids that referenced this issue Oct 17, 2024
Fixes NVIDIA#11532.

This commit introduces a RapidsErrorUtils shim for Databricks 14.3, to
deal with the new error messages thrown for large array/sequences.

This should fix the failure in `collection_ops_test.py::test_sequence_too_long_sequence`
on Databricks 14.3.

Signed-off-by: MithunR <[email protected]>
mythrocks added a commit to mythrocks/spark-rapids that referenced this issue Oct 18, 2024
Fixes NVIDIA#11532.

This commit introduces a RapidsErrorUtils shim for Databricks 14.3, to
deal with the new error messages thrown for large array/sequences.

This should fix the failure in `collection_ops_test.py::test_sequence_too_long_sequence`
on Databricks 14.3.

Signed-off-by: MithunR <[email protected]>
mythrocks added a commit to mythrocks/spark-rapids that referenced this issue Oct 18, 2024
Fixes NVIDIA#11532.

This commit introduces a RapidsErrorUtils shim for Databricks 14.3, to
deal with the new error messages thrown for large array/sequences.

This should fix the failure in `collection_ops_test.py::test_sequence_too_long_sequence`
on Databricks 14.3.

Signed-off-by: MithunR <[email protected]>
@sameerz sameerz added the task Work required that improves the product but is not user facing label Oct 19, 2024
mythrocks added a commit that referenced this issue Oct 22, 2024
* Fix `collection_ops_test` for Databricks 14.3

Fixes #11532.

This commit introduces a RapidsErrorUtils shim for Databricks 14.3, to
deal with the new error messages thrown for large array/sequences.

This should fix the failure in `collection_ops_test.py::test_sequence_too_long_sequence`
on Databricks 14.3.

Signed-off-by: MithunR <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Work required that improves the product but is not user facing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants