LuciferYang commented on PR #55410: URL: https://github.com/apache/spark/pull/55410#issuecomment-5493181742
The failing `pyspark-connect-old-client` check comes from the behavior change, not from flakiness. That job runs `branch-4.0`'s `pyspark-connect` tests against a server from this build, and `branch-4.0`'s copy of `test_nested_dataframes` still reads the batch DataFrame's temp view back through the client session. It fails on the `spark.sql` call after `processAllAvailable()` returns, so the old client drives the new server to completion; only that assertion breaks. #58446 guards that test on `branch-4.0` with `SPARK_SKIP_CONNECT_COMPAT_TESTS`, as SPARK-52077 did for `ArrowUDTFParityTests`. It needs to land before this job can go green here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
