[JBoss JIRA] (JBIDE-15870) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15870:
----------------------------------
Summary: 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
Key: JBIDE-15870
URL: https://issues.jboss.org/browse/JBIDE-15870
Project: Tools (JBoss Tools)
Issue Type: Task
Components: server
Affects Versions: 4.1.1.Beta1
Reporter: Nick Boldt
Priority: Critical
*1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component:*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
# [org.jboss.tools.as.test.core.parametized.server.publishing.defect.ClosedP...] (failing for 2 builds)
[Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for server component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.as.test.core.parametized.server.publishing.defect.ClosedProjectPublishTest : testOpenClosedProject{color} (failing for 2 builds)
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-server_41/141/testReport/org.jboss.tools.as.test.core.parametized.server.publishing.defect/ClosedProjectPublishTest/testOpenClosedProject}
<case>
<age>2</age>
<className>org.jboss.tools.as.test.core.parametized.server.publishing.defect.ClosedProjectPublishTest</className>
<duration>2.136</duration>
<errorStackTrace>junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertFalse(Assert.java:39)
at junit.framework.Assert.assertFalse(Assert.java:47)
at junit.framework.TestCase.assertFalse(TestCase.java:219)
at org.jboss.tools.as.test.core.parametized.server.publishing.defect.ClosedProjectPublishTest.testOpenClosedProject(ClosedProjectPublishTest.java:94)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
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:85)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
</errorStackTrace>
<failedSince>140</failedSince>
<name>testOpenClosedProject</name>
<skipped>false</skipped>
<status>FAILED</status>
</case>
{code}
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2818) Text in Early Access and Update page needs minor editing
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2818?page=com.atlassian.jira.plugin.... ]
Michelle Murray edited comment on JBDS-2818 at 11/5/13 6:28 PM:
----------------------------------------------------------------
Checked the following and they look good:
https://devstudio.jboss.com/updates/7.0/
https://devstudio.jboss.com/updates/7.0-staging/
https://devstudio.jboss.com/updates/7.0-development/
For Early Access, the "Release Notes & Documentation" has two versions of text. I am assuming one will be commented out depending on the status of release notes at the time of release? [~nickboldt] can you comment.
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma...
was (Author: mmurray):
Checked:
https://devstudio.jboss.com/updates/7.0/
https://devstudio.jboss.com/updates/7.0-staging/
https://devstudio.jboss.com/updates/7.0-development/
They look good. Closing JIRA.
> Text in Early Access and Update page needs minor editing
> --------------------------------------------------------
>
> Key: JBDS-2818
> URL: https://issues.jboss.org/browse/JBDS-2818
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation
> Affects Versions: 7.0.1.GA
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Fix For: 7.1.0.CR1, 8.0.0.Alpha1
>
>
> Both of these templates need the text modifying (to fit Red Hat writing style and 508 compliance):
> https://devstudio.jboss.com/updates/7.0/
> https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html
> *Common text modifications:*
> * Section "Installation :: Core Tooling"
> {quote}
> 1. If not already installed, download and install Oracle JDK or OpenJDK 7 (or 6).
> 2. Download the JBDS universal installer from <link>.
> 3. To start the installer, double-click the installer file or in a CLI enter java -jar jbdevstudio-*.jar
> {quote}
> * Section "Looking for JBoss EAP ..."
> Logo has changed, now just logotype. Looking for link.
> * Section "Getting Started Guide:"
> {quote}
> Adding *JBoss* EAP to JBDS
> {quote}
> *Early Access text modifications:*
> * Title should be "*Red Hat* JBoss Developer Studio ......"
> * Intro text
> {quote}
> We wish to give customers and users early access to *JBoss Developer Studio* so *that* we can make the next version of JBoss Developer Studio an even better environment for developing with and for Red Hat JBoss Middleware.
> {quote}
> *Updates text modifications*
> * Why do we have this text? I ask because, for example, in https://devstudio.jboss.com/updates/7.0/, on the right-hand side the "installer" link in installation step 2 takes you to https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html where you can download what looks like the GA version without subscription or opting in to a trial. Also you can get JBDS BYOE without subscription or trial on Eclipse marketplace. Seems the text is outdated but I don't know all the ins and outs of JBDS marketing and alike - hence asking the question.
> {quote}
> If you do not already have a copy of JBoss Developer Studio, you can purchase a subscription or get a
> 30-day Free Trial from here: https://access.redhat.com/downloads/.
> {quote}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15869) Test failure in org.jboss.tools.cdi.text.ext.test
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15869:
----------------------------------
Summary: Test failure in org.jboss.tools.cdi.text.ext.test
Key: JBIDE-15869
URL: https://issues.jboss.org/browse/JBIDE-15869
Project: Tools (JBoss Tools)
Issue Type: Task
Components: cdi
Affects Versions: 4.1.1.Beta1
Reporter: Nick Boldt
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/120/console}
13:39:46 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details. -> [Help 1]
13:39:46 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details.
{code}
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/ws/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/target/work/data/.metadata/.log}
!ENTRY org.eclipse.osgi 4 0 2013-11-05 11:42:47.049
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]{code}
--
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
12 years, 5 months
[JBoss JIRA] (JBDS-2818) Text in Early Access and Update page needs minor editing
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2818?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2818:
---------------------------------------
Checked:
https://devstudio.jboss.com/updates/7.0/
https://devstudio.jboss.com/updates/7.0-staging/
https://devstudio.jboss.com/updates/7.0-development/
They look good. Closing JIRA.
> Text in Early Access and Update page needs minor editing
> --------------------------------------------------------
>
> Key: JBDS-2818
> URL: https://issues.jboss.org/browse/JBDS-2818
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation
> Affects Versions: 7.0.1.GA
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Fix For: 7.1.0.CR1, 8.0.0.Alpha1
>
>
> Both of these templates need the text modifying (to fit Red Hat writing style and 508 compliance):
> https://devstudio.jboss.com/updates/7.0/
> https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html
> *Common text modifications:*
> * Section "Installation :: Core Tooling"
> {quote}
> 1. If not already installed, download and install Oracle JDK or OpenJDK 7 (or 6).
> 2. Download the JBDS universal installer from <link>.
> 3. To start the installer, double-click the installer file or in a CLI enter java -jar jbdevstudio-*.jar
> {quote}
> * Section "Looking for JBoss EAP ..."
> Logo has changed, now just logotype. Looking for link.
> * Section "Getting Started Guide:"
> {quote}
> Adding *JBoss* EAP to JBDS
> {quote}
> *Early Access text modifications:*
> * Title should be "*Red Hat* JBoss Developer Studio ......"
> * Intro text
> {quote}
> We wish to give customers and users early access to *JBoss Developer Studio* so *that* we can make the next version of JBoss Developer Studio an even better environment for developing with and for Red Hat JBoss Middleware.
> {quote}
> *Updates text modifications*
> * Why do we have this text? I ask because, for example, in https://devstudio.jboss.com/updates/7.0/, on the right-hand side the "installer" link in installation step 2 takes you to https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html where you can download what looks like the GA version without subscription or opting in to a trial. Also you can get JBDS BYOE without subscription or trial on Eclipse marketplace. Seems the text is outdated but I don't know all the ins and outs of JBDS marketing and alike - hence asking the question.
> {quote}
> If you do not already have a copy of JBoss Developer Studio, you can purchase a subscription or get a
> 30-day Free Trial from here: https://access.redhat.com/downloads/.
> {quote}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15868) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15868:
----------------------------------
Summary: 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
Key: JBIDE-15868
URL: https://issues.jboss.org/browse/JBIDE-15868
Project: Tools (JBoss Tools)
Issue Type: Task
Components: maven
Affects Versions: 4.1.1.Beta1
Reporter: Nick Boldt
Priority: Critical
*1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component:*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
# [org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest|https://je...] (failing for 18 builds)
[Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for maven component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest : testJBIDE11570_constraintViolations{color} (failing for 18 builds)
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-central_41/103/testReport/org.jboss.tools.maven.configurators.tests/SeamConfiguratorTest/testJBIDE11570_constraintViolations}
<case>
<age>18</age>
<className>org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest</className>
<duration>1.229</duration>
<errorStackTrace>java.lang.NullPointerException
at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingFiles(VirtualFile.java:104)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingResources(VirtualFile.java:93)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.exists(VirtualResource.java:88)
at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getNonBinaryComponentManifest(ManifestUtilities.java:124)
at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifest(ManifestUtilities.java:81)
at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifestClasspath(ManifestUtilities.java:147)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getManifestClasspath(J2EEModuleVirtualComponent.java:248)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:368)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:107)
at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:746)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:865)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:289)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:216)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:326)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:324)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:299)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:286)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:273)
at org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest.testJBIDE11570_constraintViolations(SeamConfiguratorTest.java:132)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
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:85)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
at java.lang.Thread.run(Thread.java:662)
</errorStackTrace>
<failedSince>86</failedSince>
<name>testJBIDE11570_constraintViolations</name>
<skipped>false</skipped>
<status>FAILED</status>
<stdout>TEST-SETUP: testJBIDE11570_constraintViolations
Restoring user settings file: /home/hudson/.m2/settings.xml
</stdout>
</case>
{code}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15867) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for central component
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15867:
----------------------------------
Summary: 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for central component
Key: JBIDE-15867
URL: https://issues.jboss.org/browse/JBIDE-15867
Project: Tools (JBoss Tools)
Issue Type: Task
Components: central
Affects Versions: 4.1.1.Beta1
Reporter: Nick Boldt
Priority: Critical
*1 Test Failure(s) in JBIDE 4.1.1.Beta1 for central component:*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
# [org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest|https://je...] (failing for 18 builds)
[Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for central component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest : testJBIDE11570_constraintViolations{color} (failing for 18 builds)
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-central_41/103/testReport/org.jboss.tools.maven.configurators.tests/SeamConfiguratorTest/testJBIDE11570_constraintViolations}
<case>
<age>18</age>
<className>org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest</className>
<duration>1.229</duration>
<errorStackTrace>java.lang.NullPointerException
at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingFiles(VirtualFile.java:104)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingResources(VirtualFile.java:93)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.exists(VirtualResource.java:88)
at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getNonBinaryComponentManifest(ManifestUtilities.java:124)
at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifest(ManifestUtilities.java:81)
at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifestClasspath(ManifestUtilities.java:147)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getManifestClasspath(J2EEModuleVirtualComponent.java:248)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:368)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:107)
at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:746)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:865)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:289)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:216)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:326)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:324)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:299)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:286)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:273)
at org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest.testJBIDE11570_constraintViolations(SeamConfiguratorTest.java:132)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
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:85)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
at java.lang.Thread.run(Thread.java:662)
</errorStackTrace>
<failedSince>86</failedSince>
<name>testJBIDE11570_constraintViolations</name>
<skipped>false</skipped>
<status>FAILED</status>
<stdout>TEST-SETUP: testJBIDE11570_constraintViolations
Restoring user settings file: /home/hudson/.m2/settings.xml
</stdout>
</case>
{code}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15853) plugins w/o test classes should not be set to packaging=eclipse-test-plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15853?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15853 at 11/5/13 5:37 PM:
-------------------------------------------------------------
Fixed in master (which is sort of Beta1), so resolving for that fixversion.
First spin:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... >=103
was (Author: nickboldt):
Fixed in master (which is sort of Beta1), so resolving for that fixversion.
> plugins w/o test classes should not be set to packaging=eclipse-test-plugin
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15853
> URL: https://issues.jboss.org/browse/JBIDE-15853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Beta1
>
>
> 4 plugins in jbosstools-integration-tests have no test classes, but are set via their pom to packaging type eclipse-test-plugin instead of eclipse-plugin.
> As a result, these four plugins fail to run tests and the resulting build is red.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integration-tests.aggregate_master/101/consoleFull}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.archives.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.common.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.ws.reddeer: No tests found.
> {code}
> I propose that if these plugins are meant to be framework/API code, containing no actual JUnit tests to run, that their poms be changed as follows:
> {code}
> - <packaging>eclipse-test-plugin</packaging>
> + <packaging>eclipse-plugin</packaging>
> {code}
> And they be moved from
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te...
> into
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-15853) plugins w/o test classes should not be set to packaging=eclipse-test-plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15853?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-15853:
----------------------------------
Assignee: Nick Boldt
> plugins w/o test classes should not be set to packaging=eclipse-test-plugin
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15853
> URL: https://issues.jboss.org/browse/JBIDE-15853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> 4 plugins in jbosstools-integration-tests have no test classes, but are set via their pom to packaging type eclipse-test-plugin instead of eclipse-plugin.
> As a result, these four plugins fail to run tests and the resulting build is red.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integration-tests.aggregate_master/101/consoleFull}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.archives.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.common.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.ws.reddeer: No tests found.
> {code}
> I propose that if these plugins are meant to be framework/API code, containing no actual JUnit tests to run, that their poms be changed as follows:
> {code}
> - <packaging>eclipse-test-plugin</packaging>
> + <packaging>eclipse-plugin</packaging>
> {code}
> And they be moved from
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te...
> into
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
--
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
12 years, 5 months