From http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-3.1.0.beta1/54/co..., snippet of log which shows test running and failing. See attached.

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, 3.1.0.beta1 Reporter: Nick Boldt Attachments: JBDS1130.log.txt 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.

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, 3.1.0.beta1 Reporter: Nick Boldt Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

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 Components: seam Affects Versions: 3.0.0.CR3, 3.1.0.beta1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 3.0.1.GA Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear -------------------------------------------------------------------------------- Key: JBDS-1130 URL: https://jira.jboss.org/browse/JBDS-1130 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 3.0.0.CR3, 3.1.0.beta1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 3.0.x, 3.1.0.beta1 Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear -------------------------------------------------------------------------------- Key: JBDS-1130 URL: https://jira.jboss.org/browse/JBDS-1130 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 3.0.0.CR3, 4.0.0.M1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 3.0.x, 4.0.0.M2 Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear -------------------------------------------------------------------------------- Key: JBDS-1130 URL: https://jira.jboss.org/browse/JBDS-1130 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 3.0.0.CR3, 4.0.0.M1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 3.0.x, 4.0.0.M2 Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear -------------------------------------------------------------------------------- Key: JBDS-1130 URL: https://jira.jboss.org/browse/JBDS-1130 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 3.0.0.CR3, 4.0.0.M1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 4.0.0.Beta1 Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear -------------------------------------------------------------------------------- Key: JBDS-1130 URL: https://jira.jboss.org/browse/JBDS-1130 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 3.0.0.CR3, 4.0.0.M1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 4.0.0.Beta2 Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.

SeamValidatorsAllTests fail intermittently, causing 38 tests to appear/disappear -------------------------------------------------------------------------------- Key: JBDS-1130 URL: https://jira.jboss.org/browse/JBDS-1130 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 3.0.0.CR3, 4.0.0.M1 Reporter: Nick Boldt Assignee: Daniel Azarov Fix For: 4.0.0.Beta2 Attachments: JBDS1130.log.txt, JBDS1130.test.workspace.log.SeamVal.txt 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.