Skip to content

Conversation

@LuciferYang
Copy link
Contributor

What changes were proposed in this pull request?

This pr simplify assertions to fix pyspark-connect test failed with Scala 2.13.

Why are the changes needed?

Fix Scala 2.13 daily test:

Traceback (most recent call last):
  File "/__w/spark/spark/python/pyspark/sql/tests/connect/test_connect_basic.py", line 337, in test_alias
    self.assertIn("Buffer(this, is, not)", str(exc.exception))
AssertionError: 'Buffer(this, is, not)' not found in '<_MultiThreadedRendezvous of RPC that terminated with:\n\tstatus = StatusCode.UNKNOWN\n\tdetails = "[INTERNAL_ERROR] Found the unresolved operator: \'Project [id#24L AS List(this, is, not)]"\n\tdebug_error_string = "UNKNOWN:Error received from peer ipv4:127.0.0.1:15002 {created_time:"2022-11-21T19:25:59.902777537+00:00", grpc_status:2, grpc_message:"[INTERNAL_ERROR] Found the unresolved operator: \\\'Project [id#24L AS List(this, is, not)]"}"\n>'

The error message with Scala 2.13 contains List(this, is, not) instead of ArrayBuffer(this, is, not).

Does this PR introduce any user-facing change?

No, just for test

How was this patch tested?

Pass GitHub Actions

@LuciferYang LuciferYang changed the title [SPARK-40809][CONNECT][TESTS] Fix pyspark-connect test failed with Scala 2.13 [SPARK-40809][SQL][CONNECT][PYTHON][TESTS] Fix pyspark-connect test failed with Scala 2.13 Nov 22, 2022
@LuciferYang LuciferYang changed the title [SPARK-40809][SQL][CONNECT][PYTHON][TESTS] Fix pyspark-connect test failed with Scala 2.13 [SPARK-40809][CONNECT][PYTHON][TESTS] Fix pyspark-connect test failed with Scala 2.13 Nov 22, 2022
@LuciferYang
Copy link
Contributor Author

dup with #38752, close this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant