[
https://issues.apache.org/jira/browse/CAMEL-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521780#comment-17521780
]
Claus Ibsen commented on CAMEL-17948:
-------------------------------------
I think the 2nd pr have made some unit test very slow (they timeout after 10
sec) instead of passing quicker.
I noticed that camel-yaml-dsl the KameletLoaderTest takes 20 sec, before it was
< 1 sec.
Now testing camel-core its also hanging at slow tests - as testing camel-core
usually takes < 5 min on my computer.
> Race condition in MockEndpoint with PER_CLASS tests
> ---------------------------------------------------
>
> Key: CAMEL-17948
> URL: https://issues.apache.org/jira/browse/CAMEL-17948
> Project: Camel
> Issue Type: Bug
> Components: camel-mock
> Affects Versions: 3.16.0
> Reporter: Nicolas Filotto
> Assignee: Nicolas Filotto
> Priority: Major
> Fix For: 3.17.0
>
>
> While working on CAMEL-17945, I realized that the tests with the scope
> {{PER_CLASS}} leveraging the {{MockEndpoint}} to define their assertions can
> fail randomly because of a race condition issue. Indeed, with the current
> code, a message of a previous test method can potentially call the method
> {{countDown}} on the latch of the following test method causing unexpected
> behavior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
