You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by gu...@apache.org on 2026/06/27 09:30:51 UTC

(spark) branch branch-4.x updated: [SPARK-57711][SQL][TEST][FOLLOWUP] Fix linter failure

This is an automated email from the ASF dual-hosted git repository.

HyukjinKwon pushed a commit to branch branch-4.x
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/branch-4.x by this push:
     new e07a9c0c70bc [SPARK-57711][SQL][TEST][FOLLOWUP] Fix linter failure
e07a9c0c70bc is described below

commit e07a9c0c70bc41f04821a13c574975fcbf0fcf19
Author: Kousuke Saruta <sa...@apache.org>
AuthorDate: Sat Jun 27 18:30:27 2026 +0900

    [SPARK-57711][SQL][TEST][FOLLOWUP] Fix linter failure
    
    ### What changes were proposed in this pull request?
    This PR fixes a liter failure which is introduced by #56790.
    https://github.com/HyukjinKwon/spark/actions/runs/28169229008/job/83432207959
    ```
    Had test failures in pyspark.sql.tests.connect.test_parity_python_streaming_datasource with python3.12; see logs.
    Error:  running /__w/spark/spark/python/run-tests --modules=pyspark-streaming,pyspark-structured-streaming,pyspark-structured-streaming-connect --parallelism=1 --python-executables=python3.12 ; received return code 255
    Error: Process completed with exit code 19.
    ```
    
    ### Why are the changes needed?
    To recover CI.
    
    ### Does this PR introduce _any_ user-facing change?
    No.
    
    ### How was this patch tested?
    GA.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    No.
    
    Closes #56829 from sarutak/fix-SQLAppStatusListenerSuit-style.
    
    Authored-by: Kousuke Saruta <sa...@apache.org>
    Signed-off-by: Hyukjin Kwon <hy...@databricks.com>
    (cherry picked from commit 2d7c3210ed30ccaf2b4b635ee67dfd4a94a84761)
    Signed-off-by: Hyukjin Kwon <hy...@databricks.com>
---
 .../apache/spark/sql/execution/ui/SQLAppStatusListenerSuite.scala | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/sql/core/src/test/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListenerSuite.scala b/sql/core/src/test/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListenerSuite.scala
index 6af000519aad..9230eb48dcca 100644
--- a/sql/core/src/test/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListenerSuite.scala
+++ b/sql/core/src/test/scala/org/apache/spark/sql/execution/ui/SQLAppStatusListenerSuite.scala
@@ -1126,10 +1126,10 @@ class SQLAppStatusListenerMemoryLeakSuite extends SparkFunSuite {
         // DAGScheduler notifies the job waiter -- unblocking the failing action on this thread --
         // *before* it posts SparkListenerJobEnd to the listener bus (see
         // DAGScheduler.failJobAndIndependentStages). That trailing JobEnd can therefore still be in
-        // flight when this thread calls waitUntilEmpty() above; if it is enqueued just after the bus
-        // is drained, the failed execution never reaches the cleanup threshold and lingers in
-        // liveExecutions. Poll with eventually() so the trailing end event is delivered and the live
-        // entries drain, rather than asserting once immediately.
+        // flight when this thread calls waitUntilEmpty() above; if it is enqueued just after the
+        // bus is drained, the failed execution never reaches the cleanup threshold and lingers in
+        // liveExecutions. Poll with eventually() so the trailing end event is delivered and the
+        // live entries drain, rather than asserting once immediately.
         eventually(timeout(5.seconds), interval(10.milliseconds)) {
           assert(statusStore.listener.get.noLiveData())
         }


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org