rebelwithoutacause opened a new pull request, #6848: URL: https://github.com/apache/jmeter/pull/6848
## Summary `batchTestSchedulerWithTimer` failed on macOS / JDK 25 in [CI run 40919458824](https://github.com/apache/jmeter/actions/runs/40919458824/job/123644550105): ``` WARN o.a.j.p.j.s.J.JSRCheckDuration: Duration 7338 exceeded expected duration of 7000 ``` The tearDown check measures time from the setUp sampler, so the 2s margin over the 5s scheduler duration also has to cover setUp thread exit, the forced GC before the main groups start, thread start and join, the tearDown group starting, and Groovy compilation of the check script. On slow CI workers this overhead can go past 2s. The engine itself behaves correctly: `JMeterThread.delay()` and `TestAction` cap their sleeps at the scheduler end time via `TimerService.adjustDelay`. ## Change - Raise the margin from 2s to 5s (limit 10s). If the scheduler stops interrupting the 20s pauses (Bugs 60797, 60049), the check still fails clearly. - Update the test plan comment to explain the margin. The expected `.csv`/`.xml` outputs are unchanged. ## Testing - `./gradlew :src:dist-check:batchTestSchedulerWithTimer` passes locally (Windows, JDK 21). 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
