[JBoss JIRA] Created: (JBDS-1130) SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear
by Nick Boldt (JIRA)
SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear
--------------------------------------------------------------------------------
Key: JBDS-1130
URL: https://jira.jboss.org/jira/browse/JBDS-1130
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 3.0.0.CR3
Reporter: Nick Boldt
Comparing the test output from JBT 3.1.0 builds:
http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.1.0.CR3/53/tes... (2264 tests, run on soa3-RHEL5-x86)
http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.1.0.CR3/56/tes... (2226 tests, run on on vmg18-rhel5-x86_64)
In both cases the SVN source revisions input to the build are the same; however, in build #53, 38 more tests are run than in build #56.
Similarly for JBDS:
http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-3.0.0.CR3/45/test... (2264 tests, run on hudson1-rhel5-x86_64)
http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-3.0.0.CR3/46/test... (2226 tests, run on hudson1-rhel5-x86_64)
Again, the SVN source revisions input to the build are the same; however, once again we have a discrepancy of 38 tests between builds.
--
The difference between these two in both cases is that the SeamValidatorsAllTests suite (38 tests) does not return any results because it times out before it can complete.
Can this test suite be broken up into smaller pieces so that it will run consistently on all hudson slaves? Note that it's apparently not a 32- vs. 64-bit issue because both #45 and #46 ran on the same slave node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBDS-1342) JBDS 4.0M2 AS6M5
by Burr Sutter (JIRA)
JBDS 4.0M2 AS6M5
----------------
Key: JBDS-1342
URL: https://jira.jboss.org/browse/JBDS-1342
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: seam
Affects Versions: 4.0.0.M2
Reporter: Burr Sutter
New Seam Project fails to deploy to AS6M5
when it does fail, then the server will continue to throw up error messages because it is trying to load the failing .war from the workspace deploy directory
workspace4m2\.metadata\.plugins\org.jboss.ide.eclipse.as.core
The only workaround that I have found so far is to delete the server and the runtime, recreate both. And on the second setup, change the server settings to use the default/deploy instead of the workspace deploy
Deleting the workspace deploy dir
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6918) seam.ui.test failures: Content Assistant returned no proposals OR Settings page is not valid: Model source folder "/TestSeamSettingsPreferencesPage" does not exist.
by Nick Boldt (JIRA)
seam.ui.test failures: Content Assistant returned no proposals OR Settings page is not valid: Model source folder "/TestSeamSettingsPreferencesPage" does not exist.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6918
URL: https://jira.jboss.org/browse/JBIDE-6918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.Beta
Reporter: Nick Boldt
Assignee: Alexey Kazakov
These tests have been failing consistently for the past 12 builds:
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.Seam Project New Wizard Tests
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testFrameworkComponents
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testMessages
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testVarAttributes
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testInterface
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testSeamELContentAssist
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testSeamELContentAssistJbide1645
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testSettingsPage
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBDS-982) Request adding a Server during the installation wizard
by Jim Tyrrell (JIRA)
Request adding a Server during the installation wizard
------------------------------------------------------
Key: JBDS-982
URL: https://jira.jboss.org/jira/browse/JBDS-982
Project: JBoss Developer Studio
Issue Type: Feature Request
Environment: JBDS 3.0 M4 on Linux JDK 6
Reporter: Jim Tyrrell
It would be nice when selecting for example an existing SOA-P install to have available in the server view, a way to validate what I have selected is correct. For example I was selecting /jboss-soa-p.4.3.0/jboss-as and it should have been /jboss-soa-p.4.3.0 instead. It would be nice if some validation could be done and the next button would be greyed out not active unless the expected correct path was selected. I am not sure if the path should be /jboss-soa-p.4.3.0/jboss-as or /jboss-soa-p.4.3.0 but part of me thinks this should be /jboss-soa-p.4.3.0/jboss-as and not the way it is today.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months