[jbosstools-issues] [JBoss JIRA] (JBIDE-12947) test failure in org.jboss.tools.drools.ui.bot.test causes soa tooling tests site to fail to build
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Fri Oct 26 15:15:02 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729543#comment-12729543 ]
Nick Boldt commented on JBIDE-12947:
------------------------------------
Job updated to run in this order: build w/o running tests (passes), publish, build w/ test (and fail).
> test failure in org.jboss.tools.drools.ui.bot.test causes soa tooling tests site to fail to build
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12947
> URL: https://issues.jboss.org/browse/JBIDE-12947
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: drools, SOA Runtime Detection, SOA Tooling
> Affects Versions: 4.0.0.Alpha1-SOA
> Reporter: Nick Boldt
> Assignee: Kris Verlaenen
> Fix For: 4.0.0.CR1
>
>
> When building the soa tooling tests site
> {code}
> git clone git://github.com/jbosstools/jbosstools-build-sites.git build-sites
> cd ~/build-sites/aggregate/soatests-site; mvn install
> {code}
> the drools ui bot test fails:
> {code}
> java.io.FileNotFoundException: File '/home/jgargula/Programs/jboss-eap-5.1/jboss-as' does not exist or is not directory
> at org.jboss.tools.ui.bot.ext.config.TestConfiguration.checkDirExists(TestConfiguration.java:198)
> at org.jboss.tools.ui.bot.ext.config.TestConfiguration.checkConfig(TestConfiguration.java:141)
> at org.jboss.tools.ui.bot.ext.config.TestConfiguration.initialize(TestConfiguration.java:93)
> at org.jboss.tools.ui.bot.ext.RequirementAwareSuite.<init>(RequirementAwareSuite.java:414)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:51)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:84)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71)
> at java.lang.Thread.run(Thread.java:662)
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.269 sec <<< FAILURE!
> Results :
> Tests in error:
> initializationError(org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests): File '/home/jgargula/Programs/jboss-eap-5.1/jboss-as' does not exist or is not directory
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Tools - SOA Tooling Tests ................... SUCCESS [0.989s]
> [INFO] org.jboss.tools.soa-tooling.tests ................. SUCCESS [0.035s]
> [INFO] org.jboss.tools.drools.ui.bot.test ................ FAILURE [33.672s]
> [INFO] org.jboss.tools.soa-tooling.tests.features ........ SKIPPED
> [INFO] org.jboss.tools.drools.test.feature ............... SKIPPED
> [INFO] JBoss Tools - SOA Tooling Tests Site .............. SKIPPED
> [INFO] ------------------------------------------------------------------------
> {code}
> So, either we need to fix this test, or we need to skip running it in the Jenkins job here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOATooling/job/jbosstools-4.0_trunk.soatests.aggregate/configure
> by passing in -Dmaven.test.skip to MAVEN_FLAGS
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list