HyukjinKwon opened a new pull request, #57107:
URL: https://github.com/apache/spark/pull/57107

   ### What changes were proposed in this pull request?
   
   **[DO-NOT-MERGE]** — split out from the flaky-test deflake work; the fix 
itself is verified (see CI below).
   
   The scheduled `build_sparkr_window` workflow (`Build / SparkR-only`, 
windows-2025) intermittently hangs in the **"Run SparkR tests"** step while the 
R process waits on the SparkR backend socket handshake during session 
initialization. With no step-level timeout, a stalled handshake silently 
consumes the full 120-minute job timeout and surfaces as a *cancellation* 
rather than a fast, retryable failure — this alternates roughly every other 
scheduled run.
   
   This adds `timeout-minutes: 60` to the "Run SparkR tests" step so a stalled 
handshake fails fast; successful runs finish the step well under the cap.
   
   ### Why are the changes needed?
   
   Convert a silent 2-hour job cancel into a fast, retryable failure, and stop 
the workflow from alternating red/green due to a startup hang rather than a 
real regression.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. CI-workflow-only change.
   
   ### How was this patch tested?
   
   Fork CI (`build_sparkr_window` on the fork): ✅ **PASS** — 
https://github.com/HyukjinKwon/spark/actions/runs/28906197544
   Finished in ~1h20m with tests running to completion (`══ DONE ══`); the 
watchdog did not fire, confirming it is non-disruptive to healthy runs.
   
   JIRA: https://issues.apache.org/jira/browse/SPARK-58026
   


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