[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
13 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
13 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
13 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)
Nick Boldt created JBIDE-13460:
----------------------------------
Summary: 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
13 years, 3 months
[JBoss JIRA] (JBIDE-13459) 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13459:
----------------------------------
Summary: 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform
Key: JBIDE-13459
URL: https://issues.jboss.org/browse/JBIDE-13459
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha1
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--server/165/testReport/}
Failing for 6 builds (age = 6):
Test Name Duration Age
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[60] 3.3 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[61] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[62] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[63] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[64] 2.3 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[65] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[66] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[67] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[68] 2.3 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[69] 2.9 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[70] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[71] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[72] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[73] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[74] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[75] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[76] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[77] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[78] 2.3 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[79] 2.3 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[80] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[81] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[82] 2.3 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[83] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[84] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[85] 2.9 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[86] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[87] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[88] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[89] 2.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[60] 3.4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[61] 4.2 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[62] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[63] 4.2 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[64] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[65] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[66] 4.1 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[67] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[68] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[69] 4.7 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[70] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[71] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[72] 4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[73] 4.2 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[74] 4.2 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[75] 4.1 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[76] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[77] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[78] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[79] 4 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[80] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[81] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[82] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[83] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[84] 3.5 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[85] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[86] 4.2 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[87] 3.6 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[88] 4.2 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[89] 3.7 sec 6
>>> org.jboss.tools.as.test.core.parametized.server.XPathModelTest.serverTestImpl[0] 15 ms 6
>>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 2 ms 6
>>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 1 ms 6
>>> org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[11] 20 ms 6
{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
13 years, 3 months
[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-12973:
----------------------------------
Assignee: Martin Malina (was: Nick Boldt)
Job simply copies from staging/{JOB_NAME} to a new location. It doesn't rebuild, refactor, or relabel.
It will however *replace* an existing build folder w/ new content, so you can overwrite your 0.2.0.Final folder when you respin.
I'm not 100% sure whether it merges in or wipes clean before republishing, but it doesn't really matter because when you're satisfied w/ your builds enough to call it Final, that CI-built nightly can simply be pushed to /stable/ instead of /development/ or /integration/ and we can manually delete the old cruft.
If you prefer to have uniquely names folders, consider using BUILD_NUMBER in the target folder... eg., 0.2.0.CI-${BUILD_NUMBER}
> publish reddeer update site to download.jboss.org
> -------------------------------------------------
>
> Key: JBIDE-12973
> URL: https://issues.jboss.org/browse/JBIDE-12973
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.1.x
>
>
> Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org.
> Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job.
> Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]:
> [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13454) Provide different palettes for pages in JSF and non-JSF projects
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13454?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13454:
-----------------------------------
Description:
If we open a file from the project with JSF nature then we should show the old palette.
Otherwise we should show the new one.
It's actually the same view (General->Palette) but different content.
We are going to implement a "mobile" palette for non-jsf projects.
> Provide different palettes for pages in JSF and non-JSF projects
> ----------------------------------------------------------------
>
> Key: JBIDE-13454
> URL: https://issues.jboss.org/browse/JBIDE-13454
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.0.0.Final
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Alpha1
>
>
> If we open a file from the project with JSF nature then we should show the old palette.
> Otherwise we should show the new one.
> It's actually the same view (General->Palette) but different content.
> We are going to implement a "mobile" palette for non-jsf projects.
--
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
13 years, 3 months