Closed
Description
From BessMash on mailing list:
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
Metadata
Metadata
Assignees
Labels
No labels