Bug #10672: Test failing on TestGitFindUtils (but only on CI, only on 3.1) - Rudder - Issue Tracker

Actions

Copy link

Bug #10672

closed

Test failing on TestGitFindUtils (but only on CI, only on 3.1)

Added by François ARMAND over 7 years ago. Updated over 7 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Architecture - Internal libs

Target version:

3.1.20

Pull Request:

Severity:

Trivial - no functional impact | cosmetic

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

We are seing the following error in our CI, but not on local env:

com.normation.rudder.repository.xml.TestGitFindUtils  Time elapsed: 0.025 sec  <<< ERROR!
java.lang.RuntimeException: can not create specification: com.normation.rudder.repository.xml.TestGitFindUtils
    at scala.sys.package$.error(package.scala:27)
    at org.specs2.specification.SpecificationStructure$.createSpecification(BaseSpecification.scala:97)
    at org.specs2.runner.JUnitRunner.specification$lzycompute(JUnitRunner.scala:26)
    at org.specs2.runner.JUnitRunner.specification(JUnitRunner.scala:26)
    at org.specs2.runner.JUnitRunner.args$lzycompute(JUnitRunner.scala:38)
    at org.specs2.runner.JUnitRunner.args(JUnitRunner.scala:38)
    at org.specs2.runner.JUnitRunner.selected$lzycompute(JUnitRunner.scala:28)
    at org.specs2.runner.JUnitRunner.selected(JUnitRunner.scala:28)
    at org.specs2.runner.JUnitRunner$$anon$4.selected$lzycompute(JUnitRunner.scala:46)
    at org.specs2.runner.JUnitRunner$$anon$4.selected(JUnitRunner.scala:46)
    at org.specs2.reporter.JUnitReporter$class.report(JUnitReporter.scala:44)
    at org.specs2.runner.JUnitRunner$$anon$4.report(JUnitRunner.scala:44)
    at org.specs2.runner.JUnitRunner.run(JUnitRunner.scala:51)
    at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
    at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
    at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
    at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

It may be due to a NPE or an other exception throwed during class instanciation (but only on CI).
It's only in 3.1, 4.0/4.1 are working OK on the CI for that one.