apupier opened a new pull request, #28633:
URL: https://github.com/apache/camel/pull/28633

   The test read sendResult.getExchanges() right after the receive-side mock 
was satisfied. The send route only reaches mock:sendResult once the publish to 
the topic has returned, which is not guaranteed to have happened yet, so the 
list could still be empty:
   "Received exchanges ==> expected: <1> but was: <0>".
   
   Wait for the aggregated exchange with
   sendResult.expectedMessageCount(1) + assertIsSatisfied(context), and use 
assertIsSatisfied(context) instead of a fixed 3s wait on receiveResult.
   
   How it was reproduced: the failure does not occur under natural timing 
locally (10/10 runs passed both with and without the change). To force the 
race, a temporary ".delay(1500).asyncDelayed()" was added between .to(topic) 
and .to(sendResult) in the send route:
   - original test: fails with the exact error above 
(GroupedExchangeRoundtripIT.sendGrouped:114)
   - fixed test: passes The delay was removed and is not part of this commit.
   
   Co-authored-by: IBM Bob 2.2.1
   
   # Description
   
   <!--
   - Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   -->
   
   # Target
   
   - [ ] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [ ] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   <!--
   # *Note*: trivial changes like, typos, minor documentation fixes and other 
small items do not require a JIRA issue. In this case your pull request should 
address just this issue, without pulling in other changes.
   -->
   
   # Apache Camel coding standards and style
   
   - [ ] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   <!--
   If you're unsure, you can format the pull request title like `[CAMEL-XXX] 
Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the 
appropriate JIRA issue.
   -->
   
   - [ ] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   <!--
   You can run the aforementioned command in your module so that the build 
auto-formats your code. This will also be verified as part of the checks and 
your PR may be rejected if if there are uncommited changes after running `mvn 
clean install -DskipTests`.
   
   You can learn more about the contribution guidelines at 
https://github.com/apache/camel/blob/main/CONTRIBUTING.md
   -->
   
   # AI-assisted contributions
   
   - [ ] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   


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