[
https://issues.apache.org/jira/browse/FLINK-41247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser updated FLINK-41247:
-----------------------------------
Labels: test-stability (was: )
> AbstractServerTest.testPortRangeSuccess sees an open server connection after
> the servers are closed
> ---------------------------------------------------------------------------------------------------
>
> Key: FLINK-41247
> URL: https://issues.apache.org/jira/browse/FLINK-41247
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Queryable State
> Affects Versions: 2.4.0
> Reporter: Martijn Visser
> Priority: Major
> Labels: test-stability
>
> AbstractServerTest.testPortRangeSuccess failed on the release-2.4 nightly of
> 2026-10-26 (AdaptiveScheduler profile, JDK 17, module core):
> https://github.com/apache/flink/actions/runs/40257526813/job/121366293767
> {code}
> [ERROR]
> org.apache.flink.queryablestate.network.AbstractServerTest.testPortRangeSuccess
> -- Time elapsed: 0.712 s <<< FAILURE!
> org.opentest4j.AssertionFailedError:
> expected: 0L
> but was: 1L
> at
> org.apache.flink.queryablestate.network.AbstractServerTest.testPortRangeSuccess(AbstractServerTest.java:134)
> {code}
> Line 134 checks that the second server has no connections left after both
> servers and the client are closed; the same check for the first server
> passed. FLINK-14185 fixed the same assertion failure in 2019, when both
> servers shared one stats object, and moved this check out of the server's
> close method.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
