[JBoss JIRA] (JBIDE-15871) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15871?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-15871:
-----------------------------------
Assignee: Nick Boldt (was: Rob Stryker)
Hey Nick:
Kick a GA build for me if you can. Thanks.
> 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
> -----------------------------------------------------------
>
> Key: JBIDE-15871
> URL: https://issues.jboss.org/browse/JBIDE-15871
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Labels: testfailure
> Fix For: 4.1.1.Final
>
>
> *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.Republi...] (failing for 3 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.RepublishDefectTest : testJBIDE6184_Odd_Republish_Error[0]{color} (failing for 3 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-server_41/139/testReport/org.jboss.tools.as.test.core.parametized.server.publishing.defect/RepublishDefectTest/testJBIDE6184_Odd_Republish_Error_0_}
> <case>
> <age>3</age>
> <className>org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest</className>
> <duration>7.94</duration>
> <errorDetails>expected:<false> but was:<true></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: expected:<false> but was:<true>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:174)
> at junit.framework.Assert.assertEquals(Assert.java:181)
> at junit.framework.TestCase.assertEquals(TestCase.java:341)
> at org.jboss.tools.as.test.core.parametized.server.publishing.AbstractPublishingTest.verifyList(AbstractPublishingTest.java:362)
> at org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.JBIDE6184EarHasDynProjs(RepublishDefectTest.java:137)
> at org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.testJBIDE6184_Odd_Republish_Error(RepublishDefectTest.java:111)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> 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.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>137</failedSince>
> <name>testJBIDE6184_Odd_Republish_Error[0]</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest: org.jboss.ide.eclipse.as.systemCopyServer, zipped, metadata, permod_default
> /mnt/hudson_workspace/workspace/jbosstools-server_41/sources/as/tests/org.jboss.tools.as.test.core/target/work/data/.metadata/.plugins/org.jboss.tools.as.test.core/testDeployments/1383068483553/deploy/ear1.ear
> </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, 4 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14818 at 11/26/13 10:02 AM:
---------------------------------------------------------------------
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module (see known issue JBIDE-13862). But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen.
I did a quick thread dump inspection but could not depict any suspicious thread:
http://fpaste.org/56871/47676913/
This looks rather like an UI issue, maybe some control overlay that's stealing mouse clicks or something. In a quick review of the code I could not see anything suspicious. Needs further investigation.
I dont see right now whats causing this. Any ideas, Rob?
was (Author: adietish):
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module (see known issue JBIDE-13862). But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen. I dont see right now whats causing this. Any ideas, Rob?
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 4 months
[JBoss JIRA] (JBIDE-15871) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15871?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15871:
-------------------------------------
Made a push to 4.1.x and 4.1.1.x. Not sure which build to kick though.
> 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
> -----------------------------------------------------------
>
> Key: JBIDE-15871
> URL: https://issues.jboss.org/browse/JBIDE-15871
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.1.1.Final
>
>
> *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.Republi...] (failing for 3 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.RepublishDefectTest : testJBIDE6184_Odd_Republish_Error[0]{color} (failing for 3 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-server_41/139/testReport/org.jboss.tools.as.test.core.parametized.server.publishing.defect/RepublishDefectTest/testJBIDE6184_Odd_Republish_Error_0_}
> <case>
> <age>3</age>
> <className>org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest</className>
> <duration>7.94</duration>
> <errorDetails>expected:<false> but was:<true></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: expected:<false> but was:<true>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:174)
> at junit.framework.Assert.assertEquals(Assert.java:181)
> at junit.framework.TestCase.assertEquals(TestCase.java:341)
> at org.jboss.tools.as.test.core.parametized.server.publishing.AbstractPublishingTest.verifyList(AbstractPublishingTest.java:362)
> at org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.JBIDE6184EarHasDynProjs(RepublishDefectTest.java:137)
> at org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.testJBIDE6184_Odd_Republish_Error(RepublishDefectTest.java:111)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> 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.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>137</failedSince>
> <name>testJBIDE6184_Odd_Republish_Error[0]</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest: org.jboss.ide.eclipse.as.systemCopyServer, zipped, metadata, permod_default
> /mnt/hudson_workspace/workspace/jbosstools-server_41/sources/as/tests/org.jboss.tools.as.test.core/target/work/data/.metadata/.plugins/org.jboss.tools.as.test.core/testDeployments/1383068483553/deploy/ear1.ear
> </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, 4 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14818 at 11/26/13 10:02 AM:
---------------------------------------------------------------------
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module (see known issue JBIDE-13862). But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen.
I did a quick thread dump inspection but could not depict any suspicious thread:
http://fpaste.org/56871/47676913/
This looks rather like an UI issue, maybe some control overlay that's stealing mouse clicks or something. In a quick review of the code I could not see anything suspicious. Needs further investigation.
@Rob: I dont see right now whats causing this. Any ideas?
was (Author: adietish):
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module (see known issue JBIDE-13862). But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen.
I did a quick thread dump inspection but could not depict any suspicious thread:
http://fpaste.org/56871/47676913/
This looks rather like an UI issue, maybe some control overlay that's stealing mouse clicks or something. In a quick review of the code I could not see anything suspicious. Needs further investigation.
I dont see right now whats causing this. Any ideas, Rob?
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 4 months
[JBoss JIRA] (JBIDE-13862) server adapter wizard: When creating adapter manually, the deploying project should be added automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-13862:
----------------------------------------
Assignee: Max Rydahl Andersen (was: Andre Dietisheim)
> server adapter wizard: When creating adapter manually, the deploying project should be added automatically
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13862
> URL: https://issues.jboss.org/browse/JBIDE-13862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: server.png, server1.png, server2.png
>
>
> Deploying project is automatically added to OpenShift Server adapter after application import:
> * after application import contains the deploying project: !server.png|thumbnail!
> When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project:
> * !server2.png|thumbnail! *->* !server1.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14818:
-------------------------------------
Fix Version/s: (was: 4.2.0.Alpha1)
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 4 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14818 at 11/26/13 9:53 AM:
--------------------------------------------------------------------
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module (see known issue JBIDE-13862). But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen. I dont see right now whats causing this. Any ideas, Rob?
was (Author: adietish):
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module. But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen. I dont see right now whats causing this. Any ideas, Rob?
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 4 months
[JBoss JIRA] (JBIDE-13862) server adapter wizard: When creating adapter manually, the deploying project should be added automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13862:
------------------------------------------
According to Rob the "magic project", which holds the OpenShift git repo clone, should never get added as module. I dont know enough about the side-effects though.
[~maxandersen] Dare to comment please?
> server adapter wizard: When creating adapter manually, the deploying project should be added automatically
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13862
> URL: https://issues.jboss.org/browse/JBIDE-13862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: server.png, server1.png, server2.png
>
>
> Deploying project is automatically added to OpenShift Server adapter after application import:
> * after application import contains the deploying project: !server.png|thumbnail!
> When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project:
> * !server2.png|thumbnail! *->* !server1.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14818:
------------------------------------------
i merged this locally and this works fine for adapters that I create via Server adapter wizard. Those dont have the "magic project" (the one that hold the repo clone) listed as module. But for projects created via Application wizard, which have the magic project listed as module, the whole deployments page is frozen. I dont see right now whats causing this. Any ideas, Rob?
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 4 months
[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-14818:
----------------------------------------
Assignee: Rob Stryker (was: Andre Dietisheim)
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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, 4 months