davsclaus opened a new pull request, #29742: URL: https://github.com/apache/camel/pull/29742
## Description [CAMEL-25966](https://issues.apache.org/jira/browse/CAMEL-25966): the tests of camel-jbang-plugin-tui are on the critical path of the build and mostly waited (about 1% CPU after the first seconds). Locally the module's tests now take 20 seconds instead of 57, compile included, and the sum of the class times went from 130 to 83 seconds. - **Awaitility's default poll delay.** `await()` waits 100 ms before its first check, even when the condition already holds, and `SemanticTabTest` alone awaits 81 times. A new test helper, `TuiAwait.await()`, checks at once and then every 10 ms. The 24 test classes that statically imported `Awaitility.await` now import it instead; `atMost` stays explicit in every call. `SemanticTabTest`: 19.3s to 2.3s. - **A 10-second timeout.** `McpFacadeConfirmTest.addingAndChangingAChaosRuleAskFirstAndCheckingDoesNot` checked a chaos rule against pid 1. That is a live process but not Camel, so the check waited the full 10 seconds for an answer. It now runs with no integration selected, which fails at once and still shows that the check is not confirmed. 10.1s to 0.3s. Not in this PR: `ActionClient` keeps waiting for the full timeout when the target process does not answer. That is product code, and #29727 (CAMEL-25447) reworks how actions are answered. ## Testing The full module suite passed in three runs (2,539 tests each, 17.8 to 20 seconds). _Claude Code on behalf of davsclaus_ 🤖 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]
