JiriOndrusek opened a new pull request, #6001: URL: https://github.com/apache/camel-quarkus/pull/6001
fixes https://github.com/apache/camel-quarkus/issues/5999 This PR fixes **tests** behavior in several corner cases. 1. Better data **clearing** - whenever test writes any data. This entry is registered for the removal at the end of the execution. Moreover - it is possible to execute `clear all` which clears all queues used by the test, This behavior is described in the readme.adoc and is suggested t o use during development. 2. **Parallel** executions - it might happen (very easily) that the execution **A** may influence execution **B**. I wasn't able to use some locking mechanism, which might be present in jt400. Therefore I added a simple locking mechanism based on the keyed data queue. - Before all tests, the attempt for locking is executed . The lock is released after all. The timeout to achieve log is set to 5 mins, after which the test fails (fi lock is not achieved) - Lock is written in a keyed data queue under hardcoded key `cq.jt400.global-lock` (described in readme.adoc). - Each execution is able to remove the old lock, if it is more then 5 minutes old. - Also `clear-all` clears the lock queue, therefore there it tests can not be blocked forever. 3. More **debug logging** is added. 4. Helper method for dumping data is added. The coverage or test amount stays the same. <!-- Uncomment and fill this section if your PR is not trivial [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #. [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request. [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html --> -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
