The GitHub Actions job "Pull Requests" on pekko.git/fix/ci-remote-send-consistency-fork has failed. Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run: 95562ce27ba7c7f1739bb1abf9fbbfe1e69ba42c / 虎鸣 <[email protected]> test: isolate SendConsistency specs into separate JVM forks Motivation: ArteryTlsTcpSendConsistencyWithOneLaneSpec flakes on CI because it creates 2 ActorSystems with TLS-TCP transport and runs 1000 round-trip message exchanges via ActorSelection. When other test classes run in the same forked JVM, lingering ActorSystem threads from previous tests consume CPU and compete with the TLS operations, causing the test to exceed its 60-second timeout (30s × timefactor=2). Modification: Add Tests.Group configuration to the remote module that partitions SendConsistency test classes into their own SubProcess (forked JVM), while keeping all other remote tests in a shared "other" group. Each SendConsistency spec gets a clean JVM with no thread contention from previously-run test classes. Result: SendConsistency specs run in isolated JVM forks, eliminating cross-test thread contention that caused the 1-lane TLS-TCP variant to flake. Tests: sbt -Dpekko.test.timefactor=2 "remote / Test / testOnly *ArteryTlsTcpSendConsistencyWithOneLaneSpec" — 4/4 passed sbt "show remote / Test / testGrouping" — verified 6 SendConsistency groups + 1 "other" group References: Refs #3089 Report URL: https://github.com/apache/pekko/actions/runs/27851803431 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
