[
https://issues.apache.org/jira/browse/CAMEL-20813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852712#comment-17852712
]
Aurélien Pupier edited comment on CAMEL-20813 at 6/6/24 10:12 AM:
------------------------------------------------------------------
for some other test containers with similar problem in the past, on the
reliability side of things, I used container.withStartupAttempts(5); for
instance here
https://github.com/apache/camel/commit/b1ccf6d99f6b3459571af5b882cd1a0ece9c4bb5
It doesn't improve the performance, but had the advantage to keep the
separation between tests. (but maybe there is some kind of "clean" which can be
done)
was (Author: apupier):
for some other test containers with similar problem in the past, on the
reliability side of things, I used container.withStartupAttempts(5);
It doesn't improve the performance, but had the advantage to keep the
separation between tests. (but maybe there is some kind of "clean" which can be
done)
> camel-infinispan: tests should use singleton containers
> -------------------------------------------------------
>
> Key: CAMEL-20813
> URL: https://issues.apache.org/jira/browse/CAMEL-20813
> Project: Camel
> Issue Type: Task
> Components: camel-infinispan
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Labels: help-wanted
> Fix For: 4.7.0
>
>
> Infinispan tests are very slow and constantly unreliable. One reason for this
> is that they don't use singleton containers and keep recreating the container
> every time.
> The tests and the test infra should be adjusted for that.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)