apupier commented on PR #30388:
URL: https://github.com/apache/camel/pull/30388#issuecomment-7005791318

   > Found ~10 other test classes in camel-cxf-spring-soap with the identical 
at-risk pattern (AvailablePortFinder + no @DirtiesContext): Camel1145RouteTest, 
LoggingInterceptorInMessageModeTest, ServiceClassRefTest, 
CxfMessageHeadersRelayTest, WSRMTest, and the CxfMtom* family. None have been 
reported flaky, so they're left out of this PR to keep it minimal — may be 
worth a follow-up ticket to audit them.
   
   I think we should also apply that, they are less flaky but still it happens 
to fail with same problem on retry:
   * 
https://develocity.apache.org/s/brj46fqqjg4ja/tests/goal/org.apache.camel:camel-cxf-spring-soap:surefire:test@default-test/details/org.apache.camel.component.cxf.Camel1145RouteTest/testCamel1145Route?top-execution=2
   * 
https://develocity.apache.org/s/vglr3ckk5l2y2/tests/goal/org.apache.camel:camel-cxf-spring-soap:surefire:test@default-test/details/org.apache.camel.component.cxf.LoggingInterceptorInMessageModeTest/testInvokingServiceFromCXFClient?top-execution=1
   * 
https://develocity.apache.org/s/qrdhsklmnsjju/tests/goal/org.apache.camel:camel-cxf-spring-soap:surefire:test@default-test/details/org.apache.camel.component.cxf.soap.headers.CxfMessageHeadersRelayTest/testInHeaderCXFClientNoRelay?expanded-stacktrace=WyIxIl0&top-execution=1
   * 
https://develocity.apache.org/s/wwqjlpdtcogus/tests/goal/org.apache.camel:camel-cxf-spring-soap:surefire:test@default-test/details/org.apache.camel.component.cxf.mtom.CxfMtomRouterPayloadModeTest/testInvokingServiceFromCXFClient?top-execution=2
   
   
   with a slightly different eoor but maybe can be solved with same pattern:
   * 
https://develocity.apache.org/s/h35reqhtxh2rq/tests/goal/org.apache.camel:camel-cxf-spring-soap:surefire:test@default-test/details/org.apache.camel.component.cxf.wsrm.WSRMTest/testWSAddressing?top-execution=1
   
   not reported for ServiceClassRefTest  but I guess it won't hurt to apply it 
also.
   
   I let you decide if you prefer to handle it directly on this PR or create a 
follow-up JIra and/or PR


-- 
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]

Reply via email to