Croway opened a new pull request, #2010: URL: https://github.com/apache/camel-spring-boot/pull/2010
## Summary `FromFtpFilterTest.testFilterFilesWithARegularFile` fails on every Camel-Spring-Boot Daily run (4.22.x, main and 4.18.x), including all surefire reruns. **Root cause:** `FtpEmbeddedService` starts the FTP server in `beforeEach` with port 0 and reads the real port only after startup. Spring builds the Camel routes before `beforeEach` runs, so the first FTP test class in the JVM captures port 0. CI logs show: ``` Started route1 (ftp://admin@localhost:0/filter) ``` The service is a static field shared by all FTP test classes. Later classes pick up the port left over from the previous run, so `FromFtpFilterTest` is the only failing class because it always runs first. **Fix:** reserve a free port with `AvailablePortFinder` in the `FtpEmbeddedService` constructor. Routes then use the port the server actually listens on. The change is test-only. ## Context The other recurring 4.22.x Daily failures (jsonpath, quartz, zipfile, platform-http cookies, `CamelCatalogIT`, `CamelJooqIT`) were already addressed by b65146163cc. No Daily build has tested that commit yet, because recent runs on the `builds37` agent died when Jenkins lost its connection to the agent. ## Testing Run against a local camel 4.22.2-SNAPSHOT build: - `FromFtpFilterTest` passed 3/3 runs with `-Dsurefire.rerunFailingTestsCount=0`. Before the fix it failed on the first attempt. - The full `camel-ftp-starter` test suite passes. - Also re-ran the tests addressed by b65146163cc on current branch HEAD: jsonpath, quartz, zipfile, platform-http cookies, `CamelCatalogIT` and `CamelJooqIT` all pass. `FtpEmbeddedService` is identical on main, so the same change applies there as a follow-up. _Claude Code (Opus 5.5) on behalf of Federico Mariani_ -- 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]
