Using ParallelRunExtension causes issues with finding fixture class during execution

[BessMash]

When we're trying to utilize ParallelRunExtension in our framework, we get exceptions like:

java.lang.ClassNotFoundException: Unable to find fixture class for '[Resource: /com/bluescape/web/tests/Arithmetic.md]'. Fixture class must be named one of [com.bluescape.web.tests.Arithmetic, com.bluescape.web.tests.ArithmeticTest, com.bluescape.web.tests.ArithmeticFixture].

at org.concordion.internal.FixtureSpecificationMapper.findFixtureClass (FixtureSpecificationMapper.java:46)

at org.concordion.internal.runner.DefaultConcordionRunner.findTestClass (DefaultConcordionRunner.java:33)

at org.concordion.internal.runner.DefaultConcordionRunner.execute (DefaultConcordionRunner.java:18)

at org.concordion.ext.run.parallel.ParallelRunStrategy$1.call (ParallelRunStrategy.java:122)

at org.concordion.ext.run.parallel.ParallelRunStrategy$1.call (ParallelRunStrategy.java:117)

at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly (TrustedListenableFutureTask.java:111)

at com.google.common.util.concurrent.InterruptibleTask.run (InterruptibleTask.java:58)

at com.google.common.util.concurrent.TrustedListenableFutureTask.run (TrustedListenableFutureTask.java:75)

at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617)

at java.lang.Thread.run (Thread.java:745)

or

java.util.NoSuchElementException: null

at sun.misc.CompoundEnumeration.nextElement (CompoundEnumeration.java:59)

at java.util.ServiceLoader$LazyIterator.hasNextService (ServiceLoader.java:357)

at java.util.ServiceLoader$LazyIterator.hasNext (ServiceLoader.java:393)

at java.util.ServiceLoader$1.hasNext (ServiceLoader.java:474)

at org.concordion.internal.FixtureSpecificationMapper.getFixtureClass (FixtureSpecificationMapper.java:53)

at org.concordion.internal.FixtureSpecificationMapper.findFixtureClass (FixtureSpecificationMapper.java:40)

at org.concordion.internal.runner.DefaultConcordionRunner.findTestClass (DefaultConcordionRunner.java:33)

at org.concordion.internal.runner.DefaultConcordionRunner.execute (DefaultConcordionRunner.java:18)

at org.concordion.ext.run.parallel.ParallelRunStrategy$1.call (ParallelRunStrategy.java:122)

at org.concordion.ext.run.parallel.ParallelRunStrategy$1.call (ParallelRunStrategy.java:117)

at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly (TrustedListenableFutureTask.java:111)

at com.google.common.util.concurrent.InterruptibleTask.run (InterruptibleTask.java:58)

at com.google.common.util.concurrent.TrustedListenableFutureTask.run (TrustedListenableFutureTask.java:75)

at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617)

at java.lang.Thread.run (Thread.java:745)

We don't get such issues for every run, but for 2 out of 3 of them.

For every specification .md file we have a fixture class with the same name. For example Arithmetic.md and Arithmetic.java.

When we run our suite without ParallelRunExtension we don't see this issue.

Would be great if somebody can advise how to cure this or work around it? 

Right now we just run our suites as parallel processes with different values for concordion.output.dir

Thank you.

[Nigel Charman]

Hi, thanks for the detailed issue report.

I've pinpointed the issue and will release a new version of Concordion with the fix in a few days.

Nigel.

--
You received this message because you are subscribed to the Google Groups "concordion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concordion+...@googlegroups.com.
To post to this group, send email to conco...@googlegroups.com.
Visit this group at https://groups.google.com/group/concordion.
To view this discussion on the web, visit https://groups.google.com/d/msgid/concordion/bf5382ec-3c21-4806-ac00-87936be8fb97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nigel Charman]

Bess - this should be fixed in Concordion 2.1.2 which I've just released.