xiongbo-sjtu opened a new pull request, #43388:
URL: https://github.com/apache/spark/pull/43388

   ### Why are the changes needed?
   
   It's discovered from [Github 
Actions](https://github.com/xiongbo-sjtu/spark/actions/runs/6270601155/job/17028788767)
 that StatusTrackerSuite can run into random failures, as shown by the 
following error message.  The proposed fix is to update the unit test to remove 
the nondeterministic behavior.
   
   The fix has been made to the master branch in 
https://github.com/apache/spark/pull/43194.  This PR is meant to patch 
branch-3.5 only.
   
   ```
       [info] StatusTrackerSuite:
       [info] - basic status API usage (99 milliseconds)
       [info] - getJobIdsForGroup() (56 milliseconds)
       [info] - getJobIdsForGroup() with takeAsync() (48 milliseconds)
       [info] - getJobIdsForGroup() with takeAsync() across multiple partitions 
(58 milliseconds)
       [info] - getJobIdsForTag() *** FAILED *** (10 seconds, 77 milliseconds)
       [info] The code passed to eventually never returned normally.
              Attempted 651 times over 10.005059944000001 seconds. 
              Last failure message: Set(3, 2, 1) was not equal to Set(1, 2). 
(StatusTrackerSuite.scala:148)
   ```
   
   Full trace can be found 
[here](https://issues.apache.org/jira/browse/SPARK-45283).
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
   ```
   build/mvn package -DskipTests -pl core
   build/mvn -Dtest=none -DwildcardSuites=org.apache.spark.StatusTrackerSuite 
test
   ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   No
   


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