You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/07/08 01:41:00 UTC

[jira] [Updated] (SPARK-58026) Bound SparkR Windows test step to avoid silent 2-hour job timeout

     [ https://issues.apache.org/jira/browse/SPARK-58026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SPARK-58026:
-----------------------------------
    Labels: pull-request-available  (was: )

> Bound SparkR Windows test step to avoid silent 2-hour job timeout
> -----------------------------------------------------------------
>
>                 Key: SPARK-58026
>                 URL: https://issues.apache.org/jira/browse/SPARK-58026
>             Project: Spark
>          Issue Type: Bug
>          Components: Project Infra, R
>    Affects Versions: 5.0.0
>            Reporter: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>
> 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. Because the step has no inner timeout, a stalled handshake silently consumes the full 120-minute job timeout and is reported as a cancellation rather than a fast, retryable failure. This alternates roughly every other scheduled run.
> Add a step-level `timeout-minutes` to the "Run SparkR tests" step so a stalled handshake fails fast (successful runs complete the step in well under the cap), converting a silent 2h cancel into a fast retryable failure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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