The GitHub Actions job "Nightly Builds (1.7)" on pekko.git/main has failed. Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run: 97a92c214a66518393fc86b2b07d850d4ba43628 / He-Pin(kerr) <[email protected]> test: relax SendQueue fuzzing deadlines (#2998) Motivation: SendQueueSpec preserves high-volume wakeup coverage but its default per-expect timeout is too tight under fuzzing-mode and virtualized nightly/CI runners. Recent failures timed out while waiting for a burst or the next element even though the stress workload itself should remain unchanged. Modification: Keep the existing burst size, 100000 rounds, and first-message ordering variants, but use explicit dilated deadlines for the slow fuzzing assertions. Result: The test still exercises the same SendQueue wakeup scenarios while allowing scheduler jitter on constrained JDK 25 and Scala 3 CI runners. Tests: - JDK 25 nightly-style: sbt "remote / Test / testOnly org.apache.pekko.remote.artery.SendQueueSpec" - 5 tests succeeded / 0 failed - JDK 25 nightly-style Scala 3.3.7: sbt "++ 3.3.7" "remote / Test / testOnly org.apache.pekko.remote.artery.SendQueueSpec" - 5 tests succeeded / 0 failed - scalafmt --mode diff-ref=origin/main - scalafmt --list --mode diff-ref=origin/main - git diff --check References: None - nightly-builds.yml and PR Scala 3 SendQueueSpec timeout Report URL: https://github.com/apache/pekko/actions/runs/26548281438 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
