LinSimon-901101 opened a new pull request, #6905:
URL: https://github.com/apache/datafusion-comet/pull/6905

   ## Which issue does this PR close?
   
   Closes #6890.
   
   ## Rationale for this change
   
   A failed Spark job can unblock the test thread before its 
`SparkListenerJobEnd` is posted. `waitUntilEmpty()` can therefore return before 
that event arrives, causing the final `noLiveData()` assertion to fail 
intermittently.
   
   ## What changes are included in this PR?
   
   Backport [SPARK-57711](https://github.com/apache/spark/pull/56790), 
including its comment-formatting follow-up, to the Spark 3.4.3, 3.5.9, 4.0.4, 
4.1.3, and 4.2.0 test patches. The final assertion uses 
`eventually(timeout(5.seconds), interval(10.milliseconds))` so the trailing 
event can complete cleanup. The workload, retention-count assertions, and leak 
predicate remain unchanged.
   
   Each patch was regenerated from its matching Spark tag following the 
contributor guide. All pre-existing patch sections remain byte-for-byte 
unchanged. This is a test-only change.
   
   ## How are these changes tested?
   
   [Successful fork 
CI](https://github.com/LinSimon-901101/datafusion-comet/actions/runs/38276490367):
   
   - Native build and Spark SQL test compilation succeeded for all five 
versions.
   - The complete `sql_core-1` shard passed on each version, including 
`SQLAppStatusListenerMemoryLeakSuite`.
   - The target suite passed ten additional runs per version: 50 repetitions, 
plus its five shard executions.
   - Verified patch application against the matching Spark tags and checked the 
applied CI patches against this change.
   
   The tested revision contains this fix plus a separate fork-only validation 
workflow. That workflow is excluded from this PR.
   


-- 
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]

Reply via email to