[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1382:
-----------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.M2)
> QA build does not archive test group summary files
> --------------------------------------------------
>
> Key: JBTM-1382
> URL: https://issues.jboss.org/browse/JBTM-1382
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten.
--
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
11 years
[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ]
Michael Musgrove reopened JBTM-1382:
------------------------------------
Reopening because narayana.sh doesn't appear to be archiving the TEST-*.txt files any more. The problem is that the statement
{noformat}
mv "$WORKSPACE/qa/TEST-*.txt"
{noformat}
does not match any files because of the quotes. The fix is to remove the quotes.
> QA build does not archive test group summary files
> --------------------------------------------------
>
> Key: JBTM-1382
> URL: https://issues.jboss.org/browse/JBTM-1382
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten.
--
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
11 years
[JBoss JIRA] (JBTM-1724) blacktie-admin-service failed with wildfly-(server, jmx, wildfly-arquillian-protocol-jmx) valid
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1724?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1724:
---------------------------------
Thanks for pointing it out
> blacktie-admin-service failed with wildfly-(server, jmx, wildfly-arquillian-protocol-jmx) valid
> -----------------------------------------------------------------------------------------------
>
> Key: JBTM-1724
> URL: https://issues.jboss.org/browse/JBTM-1724
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/job/blacktie-linux32-el5/985/
> [WARNING] The POM for org.wildfly:wildfly-server:jar:8.0.0.Alpha2-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
> [WARNING] The POM for org.wildfly:wildfly-jmx:jar:8.0.0.Alpha2-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
> [WARNING] The POM for org.wildfly:wildfly-arquillian-protocol-jmx:jar:8.0.0.Alpha2-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
--
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
11 years
[JBoss JIRA] (JBTM-1674) btadmin.PauseDomainTest failed with command failure
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1674?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1674:
--------------------------------
Description:
http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1501
{noformat}
-------------------------------------------------------------------------------
Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE!
testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE!
junit.framework.AssertionFailedError: Command failed
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48)
at junit.framework.TestCase.runBare(TestCase.java:125)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy0.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
{noformat}
was:
http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1501
{noformat}
-------------------------------------------------------------------------------
Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE!
testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE!
junit.framework.AssertionFailedError: Command failed
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48)
at junit.framework.TestCase.runBare(TestCase.java:125)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy0.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
{noformat}
> btadmin.PauseDomainTest failed with command failure
> ---------------------------------------------------
>
> Key: JBTM-1674
> URL: https://issues.jboss.org/browse/JBTM-1674
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1501
> {noformat}
> -------------------------------------------------------------------------------
> Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE!
> testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command failed
> at junit.framework.Assert.fail(Assert.java:47)
> at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
> at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
> at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
> 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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {noformat}
--
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
11 years
[JBoss JIRA] (JBTM-1724) blacktie-admin-service failed with wildfly-(server, jmx, wildfly-arquillian-protocol-jmx) valid
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1724?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1724:
-------------------------------------
I expect this is because a narayana build that includes a version of the AS has not been ran on this node as yet. This issue will go after we merge blacktie and narayana repos in JBTM-1495
> blacktie-admin-service failed with wildfly-(server, jmx, wildfly-arquillian-protocol-jmx) valid
> -----------------------------------------------------------------------------------------------
>
> Key: JBTM-1724
> URL: https://issues.jboss.org/browse/JBTM-1724
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/job/blacktie-linux32-el5/985/
> [WARNING] The POM for org.wildfly:wildfly-server:jar:8.0.0.Alpha2-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
> [WARNING] The POM for org.wildfly:wildfly-jmx:jar:8.0.0.Alpha2-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
> [WARNING] The POM for org.wildfly:wildfly-arquillian-protocol-jmx:jar:8.0.0.Alpha2-SNAPSHOT is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
--
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
11 years