[JBoss JIRA] (JBIDE-16130) Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16130?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16130:
----------------------------------
Description:
Steps to reproduce:
ASSERT: Have OpenShift Enterprise connection
ASSERT: Don't have Jenkins application on the given connection
EXEC: Open wizard for new application
EXEC: Choose some application type (doesn't matter which one)
EXEC: Toggle checkbox next to jenkins cartridge
EXEC: Click on "Apply" button
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
!jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
was:
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
!jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
> Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16130
> URL: https://issues.jboss.org/browse/JBIDE-16130
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: jenkins.png
>
>
> Steps to reproduce:
> ASSERT: Have OpenShift Enterprise connection
> ASSERT: Don't have Jenkins application on the given connection
> EXEC: Open wizard for new application
> EXEC: Choose some application type (doesn't matter which one)
> EXEC: Toggle checkbox next to jenkins cartridge
> EXEC: Click on "Apply" button
> When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
> !jenkins.png!
> Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
--
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-16130) Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-16130:
-------------------------------------
Summary: Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
Key: JBIDE-16130
URL: https://issues.jboss.org/browse/JBIDE-16130
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.1.CR1
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Attachments: jenkins.png
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size. !jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them.
--
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-16130) Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16130?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16130:
----------------------------------
Attachment: jenkins.png
> Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16130
> URL: https://issues.jboss.org/browse/JBIDE-16130
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: jenkins.png
>
>
> When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size. !jenkins.png!
> Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them.
--
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-16130) Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16130?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16130:
----------------------------------
Description:
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
!jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
was:
When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size. !jenkins.png!
Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them.
> Openshift Enterprise: Creating (separate) jenkins application caused by adding jenkins client to other application does not work
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16130
> URL: https://issues.jboss.org/browse/JBIDE-16130
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: jenkins.png
>
>
> When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.
> !jenkins.png!
> Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
--
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-16128) Publish component sites to Nexus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16128:
------------------------------------
If you're not going to consume the sites, when why bother? How will you know what the performance pros/cons are if we don't stress-test the system?
Is the point of this to publish just milestones and .Final bits? Or every single nightly build? If the former, that's semi-reasonable, especially if we are planning to move toward the IS model of "components can release their Final earlier than the rest of the stack".
Thus instead of these sites:
http://download.jboss.org/jbosstools/updates/stable/kepler/core/
http://download.jboss.org/jbosstools/builds/staging/
we'd have the equivalent bits in Nexus:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
What exactly does moving to nexus get us? Automated cleanup of snapshots? We have that already. Fast downloads of both sites and zips? We have that already. Seems like all we'd be getting is another checkpoint process (deploy to staging then release from staging to public) which in a sense we already have [1], except the existing job can publish a nightly to release or a milestone to stable, not just a staged build to public.
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/
Also, are you assuming that component owners will be responsible for doing their own promotes from nexus-staging to nexus-public? If that is your assumption, I challenge it. Chances are good the real person who'll be performing that step is YOU. Because realistically, many component leads don't even know how (or want to know how) to kick their own BUILD JOBS, much less play with Nexus to promote bits.
> Publish component sites to Nexus
> --------------------------------
>
> Key: JBIDE-16128
> URL: https://issues.jboss.org/browse/JBIDE-16128
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha1
>
>
> In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
> Then we'll see what are the pros/cons of this approach.
> Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.
--
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-16079) Forge2 UI elements are not rendered correctly
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16079?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-16079:
------------------------------------
Hi Koen, I've tried on Ubuntu 12.04 LTS.
uname -a: Linux psrna-ThinkPad-T430s 3.5.0-44-generic #67~precise1-Ubuntu SMP Wed Nov 13 16:20:03 UTC 2013 i686 i686 i386 GNU/Linux
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) Server VM (build 24.45-b08, mixed mode)
> Forge2 UI elements are not rendered correctly
> ---------------------------------------------
>
> Key: JBIDE-16079
> URL: https://issues.jboss.org/browse/JBIDE-16079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Pavol Srna
> Fix For: 4.2.0.Alpha1
>
> Attachments: forge2-ui.png
>
>
> Ctrl+5 opens a list of available actions. The problem is that the items are visible only when the mouse is over.
> !forge2-ui.png!
--
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-15878) Visual Page Editor conflicts with mobile palette because of sqllite incompatibility
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15878?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-15878.
---------------------------------
Verified under the same workstation where it was failing, now it is not with JBDS 7.1.0.CR1.
Closing.
> Visual Page Editor conflicts with mobile palette because of sqllite incompatibility
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15878
> URL: https://issues.jboss.org/browse/JBIDE-15878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Beta1
> Environment: Linux (since osx and windows allows codesharing)
> Reporter: Max Rydahl Andersen
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: tablewizardfedora18.png
>
>
> We've found that like JBIDE-9144 we still have a problem mixing webkit and xulrunner.
> Test to see if it fails:
> 1 Run Linux (version from JBIDE-9144)
> 2 Create a html5 page
> {code}
> <!DOCTYPE html>
> <html>
> <head>
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.css" />
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> </head>
> <body>
> <h1>HTML 5</h1>
> </body>
> </html>
> {code}
> 3 Use a fresh workspace
> 4 Open Preferences , Ensure "Source" is set as default active editor tab for "Visual Page Editor"
> 5. Open html5 page (DO NOT OPEN VISUAL/PREVIEW TABS IN VPE!)
> 6 Open Palette, see JQueryMobile drag "Table" to the page - see preview working
> 7. Switch to Visual/Source (visual part should be enabled)
> 8. Drag another "table" to the page
> Take screenshot showing dialog with Table at the same time as VPE shows preview of html5
> 9. write down linux versoin, Java version (32/64 bit)
>
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15871?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15871 at 11/26/13 10:56 AM:
---------------------------------------------------------------
[~rob.stryker] This is the build for the 41x stream, as it's been since ... well, quite some time.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
#156 is spinning.
was (Author: nickboldt):
[~rob.stryker] This is the build for the 41x stream, as it's been since ... probably March 2013.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
#156 is spinning.
> 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-15871) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15871?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15871:
------------------------------------
[~rob.stryker] This is the build for the 41x stream, as it's been since ... probably March 2013.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
#156 is spinning.
> 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