davsclaus opened a new pull request, #29484: URL: https://github.com/apache/camel/pull/29484
_Claude Code on behalf of davsclaus_ `LocalCliConnectorJfrActionTest.reportsAnErrorWhenTheJfrConsoleIsNotOnTheClasspath` fails on its first attempt in every full run of `camel-cli-connector`, and only passes on the surefire retry (shown as a flake). **Cause:** the action and output files of the file transport are keyed on the pid (`~/.camel/<pid>-action.json`), which every test of the fork shares. `LocalCliConnectorSendActionTest` (#29459) starts a `LocalCliConnector` with the default file transport, though it dispatches its actions directly. Running at the same time as the JFR test, its connector takes the JFR test's action file, and the JFR test waits 10 seconds for an output that never comes. Running only these two classes together fails every time. **Fix (tests only):** - `LocalCliConnectorSendActionTest` gets a no-op transport, as `LocalCliConnectorSemanticLifecycleTest` already does. - `LocalCliConnectorJfrActionTest` is `@Isolated`, like the other four tests that use the pid files (`FileCliConnectorTransportTest`, `FileCliConnectorTransportStopTest`, `LocalCliConnectorFileTransportTest`, `LocalCliConnectorChaosActionTest`). It also failed in an earlier tree without the send test, so the isolation guards against any other connector polling at the same time. **Tests:** with `-Dsurefire.rerunFailingTestsCount=0`, the two classes together failed 2 of 2 runs before and passed 3 of 3 after. The full module passed 3 of 3 runs (106 tests, no flakes). 🤖 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]
