[JBoss JIRA] (JBIDE-13308) Remove cascading and rename trunk jobs to follow new naming scheme
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13308:
------------------------------------
(2013-01-31 15:43:53) nickboldt: <project>_<version>_<qualifier><more metadata>
(2013-01-31 15:52:47) maxandersen: my suggestion was simply jbt-<component>-<stream>-<what>
{code}
jbt-hibernatetools_41 (unclear if that's hibernatetools 4.1, for hibernate 4.1, or as part of jbt 4.1)
jbt-hibernatetools_master (won't have to rename it after we split off 4.1.x branch)
jbt-javaee_41
jbt-javaee_master
jbt-central_41
jbt-central_master
etc.
{code}
Or we could do this, which maps to the github project name, minus the "jbosstools-" prefix, and uses the shortest possible suffix to define the stream, assuming that if no version is stated, it's from master branch:
{code}
hibernatetools_jbt41 (won't have to rename it for every milestone)
hibernatetools_jbt (won't have to rename it after we split off 4.1.x branch)
javaee_jbt41
javaee_jbt
central_jbt41
central_jbt
and
jbosstools.flow{1-5}_jbt41 - looking at having 5 sequential flow jobs. See JBIDE-12850 #comment-12751438)
jbosstools.flow{1-5}
jbosstools.core.aggregate_jbt41
jbosstools.core.aggregate
jbosstools.webtools.aggregate_jbt41
jbosstools.webtools.aggregate
jbosstools.integrationtests.aggregate_jbt41
jbosstools.integrationtests.aggregate
devstudio_70
devstudio_trunk
etc.
{code}
> Remove cascading and rename trunk jobs to follow new naming scheme
> ------------------------------------------------------------------
>
> Key: JBIDE-13308
> URL: https://issues.jboss.org/browse/JBIDE-13308
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
>
> Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources.
--
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, 3 months
[JBoss JIRA] (JBIDE-13461) Wrong shell title in CheckForUpdatesTest in org.jboss.tools.tests.installation
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-13461:
----------------------------------
Summary: Wrong shell title in CheckForUpdatesTest in org.jboss.tools.tests.installation
Key: JBIDE-13461
URL: https://issues.jboss.org/browse/JBIDE-13461
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Final
Reporter: Pavol Srna
Assignee: Pavol Srna
Fix For: 4.1.0.Alpha1
InstallTest.continueInstall method is called in CheckForUpdatesTest, but in this case the shell title changed. It is not called "Installing Software" but "Updating Software" and therefore the CheckForUpdatesTest will fail.
--
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, 3 months
[JBoss JIRA] (JBIDE-13455) Code completion for tag names throws NPE
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13455?page=com.atlassian.jira.plugi... ]
Victor Rubezhny reassigned JBIDE-13455:
---------------------------------------
Assignee: Alexey Kazakov (was: Victor Rubezhny)
Issue is fixed. No need to add a namespace if no uri/prefix specified, so the namespace adding is just skipped in case of no uri or prefix is specified.
JUnit Test cannot be made for such case because it is too hard to emulate the typing of a text into the editor while Content Assist window is opened to
make Content Assist window to filter out existing proposals dynamically.
Please, verify.
> Code completion for tag names throws NPE
> ----------------------------------------
>
> Key: JBIDE-13455
> URL: https://issues.jboss.org/browse/JBIDE-13455
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Alpha1
> Environment: Eclipse 4.3.0.M4
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> 1. Create s JSF2 KickStart project.
> 2. Open inputname.xhtml
> 3. Ctrl+Space in the page (for the list of available tags)
> 4. The list of proposals appears. Continue to type: <h:
> 5. Select h:body. Press enter:
> {code}
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:542)
> at org.jboss.tools.jst.jsp.contentassist.computers.XmlTagCompletionProposalComputer$NameSpaceInserter.run(XmlTagCompletionProposalComputer.java:720)
> at org.jboss.tools.jst.jsp.contentassist.AutoContentAssistantProposal.apply(AutoContentAssistantProposal.java:79)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertProposal(CompletionProposalPopup.java:940)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertSelectedProposalWithMask(CompletionProposalPopup.java:891)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.verifyKey(CompletionProposalPopup.java:1323)
> at org.eclipse.jface.text.contentassist.ContentAssistant$InternalListener.verifyKey(ContentAssistant.java:808)
> at org.eclipse.jface.text.TextViewer$VerifyKeyListenersManager.verifyKey(TextViewer.java:491)
> at org.eclipse.swt.custom.StyledTextListener.handleEvent(StyledTextListener.java:65)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1401)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187)
> at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5942)
> at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5639)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1401)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1428)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:829)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3180)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:758)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2092)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5334)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4532)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8549)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1241)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2281)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3324)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1049)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:939)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:587)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:542)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1443)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1419)
> {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, 3 months
[JBoss JIRA] (JBIDE-10780) Gnome Shell crash when editing wsdl file
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10780?page=com.atlassian.jira.plugi... ]
Pavol Srna reassigned JBIDE-10780:
----------------------------------
Assignee: Andrej Podhradsky (was: Pavol Srna)
Hi Andrej, don't you know what's the status of this issue?
> Gnome Shell crash when editing wsdl file
> ----------------------------------------
>
> Key: JBIDE-10780
> URL: https://issues.jboss.org/browse/JBIDE-10780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: BPEL, UpStream
> Affects Versions: 3.3.0.M5, 3.3.0.Beta2-SOA
> Reporter: Pavol Srna
> Assignee: Andrej Podhradsky
> Priority: Blocker
> Labels: UX
> Fix For: 4.0.x
>
> Attachments: bpel-screen1.png
>
>
> This jira was found during the JBDS TestDay. Gnome Shell will crash when you edit some wsdl file. I saw this issues couple of times but cannot always reproduce.
--
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, 3 months
[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13460?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13460:
----------------------------------------
Do we have the same build result in public sites? I don't have access to VPN :(
> test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-13460
> URL: https://issues.jboss.org/browse/JBIDE-13460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Seam 2
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Kukharchuk
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/}
> Test Result
> 2 failures (-7)
> 2,118 tests (-171)
> Took 53 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4
> >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25
> {code}
> Note that we've had considerably more tests complete in the past:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure)
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure)
--
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, 3 months
[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13460?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13460:
------------------------------------
Compare the build logs and/or test results pages from the builds above to see what tests are missing:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (bad)
vs.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (good)
> test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-13460
> URL: https://issues.jboss.org/browse/JBIDE-13460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Seam 2
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Kukharchuk
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/}
> Test Result
> 2 failures (-7)
> 2,118 tests (-171)
> Took 53 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4
> >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25
> {code}
> Note that we've had considerably more tests complete in the past:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure)
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure)
--
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, 3 months
[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13460?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13460:
----------------------------------------
Victor, please take a look at these two tests.
Nick, Seam tests (and other javaee tests) should not take so long time. If it takes more then 8hrs then they just hung. But there are so many tests... Can we see what test took so long time?
> test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-13460
> URL: https://issues.jboss.org/browse/JBIDE-13460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Seam 2
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Kukharchuk
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/}
> Test Result
> 2 failures (-7)
> 2,118 tests (-171)
> Took 53 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4
> >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25
> {code}
> Note that we've had considerably more tests complete in the past:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure)
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure)
--
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, 3 months
[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13460?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-13460:
--------------------------------------
Assignee: Victor Kukharchuk (was: Alexey Kazakov)
> test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-13460
> URL: https://issues.jboss.org/browse/JBIDE-13460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Seam 2
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Kukharchuk
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/}
> Test Result
> 2 failures (-7)
> 2,118 tests (-171)
> Took 53 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4
> >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25
> {code}
> Note that we've had considerably more tests complete in the past:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure)
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure)
--
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, 3 months
[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13460?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13460:
------------------------------------
Guessing this is yet another case of "tests take more than 8hrs and Jenkins kills the thread". Do we need to set a longer timeout? Or have the tests themselves die quicker / set faster stuck-test-timeouts so the overall suite can always complete in <8hrs?
> test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-13460
> URL: https://issues.jboss.org/browse/JBIDE-13460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Seam 2
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/}
> Test Result
> 2 failures (-7)
> 2,118 tests (-171)
> Took 53 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4
> >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25
> {code}
> Note that we've had considerably more tests complete in the past:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure)
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure)
--
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, 3 months