[JBoss JIRA] (JBTM-1911) CI failure: estSocketServer::testServer (F) line: 88 /home/hudson/workspace/btny-pulls-narayana/blacktie/core/src/test/cpp/TestSocketServer.cxx
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1911?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1911:
---------------------------------
Thanks Tom,
{code}
[exec] .2013-09-06 15:46:19,318 [0x40344c0] INFO (AtmiBrokerLogc :66) - start server
[exec] 2013-09-06 15:46:19,354 [0xc996700] WARN (SocketServer :145) - could not bind on port 12345: Address already in use
[exec] --19013:1:syswrap- thread_wrapper(tid=2): exit
[exec] --19013:1:syswrap- run_a_thread_NORETURN(tid=2): post-thread_wrapper
[exec] --19013:1:syswrap- run_a_thread_NORETURN(tid=2): not last one standing
[exec] 2013-09-06 15:46:19,363 [0x40344c0] ERROR (SocketServer :211) - server on port 12345 is not running
[exec] F2013-09-06 15:46:19,402 [0x40344c0] INFO (AtmiBrokerLogc :66) - stop server
{code}
It looks like the port is used by the other application.
> CI failure: estSocketServer::testServer (F) line: 88 /home/hudson/workspace/btny-pulls-narayana/blacktie/core/src/test/cpp/TestSocketServer.cxx
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1911
> URL: https://issues.jboss.org/browse/JBTM-1911
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M5
>
>
> http://172.17.131.2/job/btny-pulls-narayana/1074/console
> Please investigate Amos:
> 1) test: TestSocketServer::testServer (F) line: 88 /home/hudson/workspace/btny-pulls-narayana/blacktie/core/src/test/cpp/TestSocketServer.cxx
> [exec] assertion failed
> [exec] - Expression: _w12pq_u
> I have marked the build as keep forever
--
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, 4 months
[JBoss JIRA] (JBTM-1674) btadmin.PauseDomainTest failed with command failure
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1674?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1674:
---------------------------------
Tom,
{code}
[0m[31m13:06:48,627 ERROR [stderr] (Thread-1057) Exception in thread "Thread-1057" java.lang.ArrayIndexOutOfBoundsException: 1
[0m[31m13:06:48,627 ERROR [stderr] (Thread-1057) at org.jboss.narayana.blacktie.jatmibroker.core.server.Client.run(SocketServer.java:268)
[0m[31m13:06:48,627 ERROR [stderr] (Thread-1057) at java.lang.Thread.run(Thread.java:722)
{code}
It looks like that there is something wrong with the received buffer but I'm not sure what happened. Also it's hard to reproduce this issue.
Amos
> 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: 6.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, 4 months
[JBoss JIRA] (JBTM-1908) Running junit tests now uselessly verbose on command line
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1908?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1908:
-----------------------------------
Yes, that sounds like a good idea. Then we just need to look at the related issue I created and wait for the surefire team to (hopefully) address the enhancement request.
> Running junit tests now uselessly verbose on command line
> ---------------------------------------------------------
>
> Key: JBTM-1908
> URL: https://issues.jboss.org/browse/JBTM-1908
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M4
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Priority: Minor
>
> Building all of TS today suddenly the output is ...
> Running com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItemUnitTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.357 sec - in com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItemUnitTest
> Running com.arjuna.ats.jts.TransactionServerUnitTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.318 sec - in com.arjuna.ats.jts.TransactionServerUnitTest
> Running com.hp.mwtests.ts.jts.context.ContextManagerUnitTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.46 sec - in com.hp.mwtests.ts.jts.context.ContextManagerUnitTest
> Running com.hp.mwtests.ts.jts.interposition.ArjunaInterpositionUnitTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.427 sec - in com.hp.mwtests.ts.jts.interposition.ArjunaInterpositionUnitTest
> What is the point of the text after the time since it duplicates the text (class) on line above anyway? Can we turn this off please?
--
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, 4 months
[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 commented on JBTM-1674:
-------------------------------------
Hi Amos,
Do you have any update on this one? There are very few existing CI issues but this one has been sat in the queue for a long time for investigation.
Many thanks,
Tom
> 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: 6.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, 4 months
[JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1572:
--------------------------------
Attachment: JBTM-1572.txt
JBTM-1572.zip
I have attached the last failed logs.
I have also set up a job to test this, however as per Mikes instructions it is not a repeating job and may make sense to convert it to run on linux if we had the time.
> a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't
> ------------------------------------------------------------------------------------------------
>
> Key: JBTM-1572
> URL: https://issues.jboss.org/browse/JBTM-1572
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Fix For: 6.0.0.Final
>
> Attachments: client.valgrind, JBTM-1572.txt, JBTM-1572.zip, server.valgrind, windbg.out
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too
--
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, 4 months