To be clearer: I meant that it's probably worth converting to parallelization via JUnit, but it's hard to know for sure now (as they need to be converted first - I don't think they are thread safe / safe for concurrent execution within the same JVM).
On Tue, Aug 23, 2022 at 7:38 PM Otavio Rodolfo Piske <angusyo...@gmail.com> wrote: > Hello, > > Do you mean for the FTP tests? I suspect not ... But they probably need to > be adjusted for running parallelized via JUnit instead of via surefire > forks (similar to what I did w/ the JMS ones) to know for sure. > > Kind regards > > On Tue, Aug 23, 2022 at 6:37 PM Karen Lease <karenlease...@gmail.com> > wrote: > >> I notice in the logfile that that tests are running in parallel using >> the surefire.forkCount. >> Is it worth instead using the Junit parallel execution parameter which >> runs tests in parallel in different worker threads instead of in >> different VMs? >> That's how the camel core tests are run. >> >> Regards, >> Karen >> >> On 23/08/2022 14:59, Otavio Rodolfo Piske wrote: >> > Actually, let me share what I have so far, because I am doing multiple >> > things at the same time and it may take a while ... So, in case anyone >> > has suggestions, this might be helpful. >> > >> > On the machine I reproduced the problem, it's currently blocked on the >> > camel-ftp tests. The tests seem to be locked because this lock (see >> also >> > the attachment): >> > >> https://github.com/apache/camel/blob/main/core/camel-api/src/main/java/org/apache/camel/support/service/BaseService.java#L144 >> > < >> https://github.com/apache/camel/blob/main/core/camel-api/src/main/java/org/apache/camel/support/service/BaseService.java#L144 >> > >> > >> > I think that one way to solve this and find the offending test, is to >> > add the @Timeout annotation on the tests. I have been trying to do this >> > whenever I can, but we have a lot of tests. I am not entirely sure it >> > would solve the problem in this particular case, but the timeout >> usually >> > helps. >> > >> > Kind regards >> > >> > >> > On Tue, Aug 23, 2022 at 2:39 PM Otavio Rodolfo Piske >> > <angusyo...@gmail.com <mailto:angusyo...@gmail.com>> wrote: >> > >> > Hi, >> > >> > I am looking at it ... I kinda managed to reproduce the problem in a >> > test host. >> > >> > >> > On Tue, Aug 23, 2022 at 12:53 PM Claus Ibsen <claus.ib...@gmail.com >> > <mailto:claus.ib...@gmail.com>> wrote: >> > >> > Hi >> > >> > Since this job then the CI server is getting stuck every time >> > >> https://ci-builds.apache.org/job/Camel/job/Apache%20Camel/job/main/546/ >> > < >> https://ci-builds.apache.org/job/Camel/job/Apache%20Camel/job/main/546/> >> > >> > I wonder if it's the maven surefire upgrade that is causing >> > something? >> > >> > >> > >> > -- >> > Claus Ibsen >> > ----------------- >> > http://davsclaus.com <http://davsclaus.com> @davsclaus >> > Camel in Action 2: https://www.manning.com/ibsen2 >> > <https://www.manning.com/ibsen2> >> > >> > >> > >> > -- >> > Otavio R. Piske >> > http://orpiske.net <http://orpiske.net> >> > >> > >> > >> > -- >> > Otavio R. Piske >> > http://orpiske.net <http://orpiske.net> >> > > > -- > Otavio R. Piske > http://orpiske.net > -- Otavio R. Piske http://orpiske.net
