He-Pin opened a new pull request, #2945: URL: https://github.com/apache/pekko/pull/2945
### Motivation The JDK 25 nightly run with virtualized dispatchers can hit load-sensitive timeouts in several stream tests and in `MixedProtocolClusterSpec` shutdown. The observed failures include `actor-system-terminate` timing out after 10 seconds and stream tests timing out while waiting for graph progress or abrupt materializer cleanup. ### Modification * Increase `ClusterTestUtil.shutdownAll` and `MixedProtocolClusterSpec` actor-system termination windows for virtualized JDK 25 nightly runs. * Make exposed stream test waits honor `pekko.test.timefactor` via dilated timeouts. * Ensure `FlowMapWithResourceSpec` abrupt materializer termination tests wait until the resource has actually been created before shutting down the materializer. ### Result This keeps the tests strict about completion and cleanup, but avoids failing under JDK 25 virtual-thread scheduling contention before the stream or actor system has had enough time to make progress. ### Verification Ran locally with JDK 25.0.1 and the nightly virtual-thread dispatcher settings: * `++ 3.3.x stream-tests/testOnly org.apache.pekko.stream.scaladsl.FlowScanSpec org.apache.pekko.stream.scaladsl.FlowMapAsyncUnorderedSpec org.apache.pekko.stream.scaladsl.FlowMapWithResourceSpec -- -z "restart properly" -z "not run more futures than configured" -z "abrupt materializer termination"` * `++ 2.13.x stream-tests/testOnly org.apache.pekko.stream.scaladsl.FlowScanSpec org.apache.pekko.stream.scaladsl.FlowMapAsyncUnorderedSpec org.apache.pekko.stream.scaladsl.FlowMapWithResourceSpec -- -z "restart properly" -z "not run more futures than configured" -z "abrupt materializer termination"` * `++ 3.3.x stream-tests/testOnly org.apache.pekko.stream.scaladsl.HubSpec` * `cluster/testOnly org.apache.pekko.cluster.MixedProtocolClusterSpec -- -z "allow a node using the pekko protocol to join the cluster (udp)"` * `git diff --check` -- 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]
