Angryrou commented on PR #11345: URL: https://github.com/apache/incubator-gluten/pull/11345#issuecomment-3706886355
Here's the summary of the 8 failed tests from the Gluten CI log — they were not on our radar because they were skipped without this PR fix. All of them are from the same test suite (ClickHouseAdaptiveQueryExecSuite.scala) and were introduced in this [commit][1] from the same PR#5310 "[GLUTEN-5309] Add UTs for Spark 3.5". According to PR#5310, the existing failed tests are ignored (skipped) and tracked separately. (cc @yma11) Could you help verify and point me to the known failed UT list? I am thinking of ignoring those failures as a quick "fix" - a real fix might be worth having separate PRs -- Let me know if this sounds good to you @jinchengchenghh @yma11 | # | Test Name | Failure Reason | |---|-----------|----------------| | 1 | Gluten - Change broadcast join to merge join | List() had size 0 instead of expected size 1 | | 2 | Gluten - Empty stage coalesced to 1-partition RDD | find(plan)(_.isInstanceOf[SortMergeJoinExecTransformer]).isDefined was false | | 3 | Gluten - Exchange reuse | 2 did not equal 1 | | 4 | Gluten - SPARK-30524: Do not optimize skew join if introduce additional shuffle | List() had size 0 instead of expected size 1 | | 5 | Gluten - SPARK-33551: Do not use AQE shuffle read for repartition | List() had length 0 instead of expected length 1 | | 6 | Gluten - SPARK-35264: Support AQE side broadcastJoin threshold | List() had size 0 instead of expected size 1 | | 7 | Gluten - SPARK-35264: Support AQE side shuffled hash join formula | 0 did not equal 1 | | 8 | Gluten - SPARK-37742: AQE reads invalid InMemoryRelation stats and mistakenly plans BHJ | Expected 1 BroadcastHashJoin but got multiple | [1]: https://github.com/apache/incubator-gluten/commit/bf6f6746622cac72cab636b9083fc8383722e078 -- 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]
