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

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

> Flaky SparkLauncherSuite.testInProcessLauncher due to short 
> connection-establishment timeout
> --------------------------------------------------------------------------------------------
>
>                 Key: SPARK-57482
>                 URL: https://issues.apache.org/jira/browse/SPARK-57482
>             Project: Spark
>          Issue Type: Test
>          Components: Spark Core, Tests
>    Affects Versions: 5.0.0
>            Reporter: DB Tsai
>            Priority: Minor
>              Labels: pull-request-available
>
> {{SparkLauncherSuite.testInProcessLauncher}} waits for the connection between 
> the in-process app and the launcher to be established by polling the app 
> handle state with {{eventually(Duration.ofSeconds(5), 
> Duration.ofMillis(10))}}. Under heavy CI load this 5-second window is too 
> short: the handle can remain in {{UNKNOWN}} for longer, causing the test to 
> fail with:
> {code}
> java.lang.IllegalStateException: Failed check after 476 tries: expected: not 
> equal but was: <UNKNOWN>.
>   at org.apache.spark.launcher.BaseSuite.eventually(BaseSuite.java:88)
>   at 
> org.apache.spark.launcher.SparkLauncherSuite.inProcessLauncherTestImpl(SparkLauncherSuite.java:162)
>   at 
> org.apache.spark.launcher.SparkLauncherSuite.testInProcessLauncher(SparkLauncherSuite.java:130)
> {code}
> The fix increases the timeout to 30 seconds with a 100ms poll interval, 
> consistent with {{waitForSparkContextShutdown}} (30s/100ms) and the other 
> {{eventually}} calls in this suite (60s/1000ms). Test-only change; no 
> production behavior is affected.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to