Re: QPID CPP 0.34: Interop Test Failure?

[Alan Conway]

On Tue, 2016-03-08 at 16:57 +, Flores, Paul A. wrote:
> What can I do to resolves these errors?  
> 
> Can I ignore them?
> 
> 
> interop_tests.CppTxTest.test_txtest2
>  fail
> ..
>  BadProcessStatus: qpid-txtest2-2 Exit code 2:
> qpid-txtest2: Transfer agents failed
> interop_tests.PythonTxTest.test_tx_sequence
> . fail
> ConnectError: Connect failed to amqp:tcp:127.0.0.1:33925: Reconnect
> disabled
> interop_tests.PythonTxTest.test_tx_simple_commit
>  fail
> ConnectError: Connect failed to amqp:tcp:127.0.0.1:33925: Reconnect
> disable
>  Totals: 7 tests, 1 passed, 0 skipped, 0 ignored, 6 failed
> ...
> Exception: Unexpected process status:
> BadProcessStatus: expected running, exit code -11: broker0 (qpidd-0)

The exit code -11 indicates that your broker crashed with a memory
error, that's why the connections failed. The problem might be specific
to transaction support if these are the only tests failing but it would
be best to know more. 

There should be a tests/interop_tests.tmp in your build dir, that shoud
contain some logs that may give more information. There may also be a
core file from the broker there, depending on how your system is set up
to handle core files.

If you have valgrind, running the test with valgrind might also give
more information, I think the valgrind output will go under the
interop_tests.tmp directory.



-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: QPID CPP 0.34: Interop Test Failure?

[Flores, Paul A.]

What can I do to resolves these errors?  

Can I ignore them?


interop_tests.CppTxTest.test_txtest2  fail
..
 BadProcessStatus: qpid-txtest2-2 Exit code 2:
qpid-txtest2: Transfer agents failed
interop_tests.PythonTxTest.test_tx_sequence . fail
ConnectError: Connect failed to amqp:tcp:127.0.0.1:33925: Reconnect disabled
interop_tests.PythonTxTest.test_tx_simple_commit  fail
ConnectError: Connect failed to amqp:tcp:127.0.0.1:33925: Reconnect disable
 Totals: 7 tests, 1 passed, 0 skipped, 0 ignored, 6 failed
...
Exception: Unexpected process status:
BadProcessStatus: expected running, exit code -11: broker0 (qpidd-0)


From: Steve Huston [shus...@riverace.com]
Sent: Tuesday, March 08, 2016 10:41 AM
To: users@qpid.apache.org
Subject: RE: QPID CPP 0.34: Interop Test Failure?

The tests try to pick an unused port, so 52652 is reasonable.

> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
> Sent: Tuesday, March 08, 2016 11:27 AM
> To: users@qpid.apache.org
> Subject: RE: QPID CPP 0.34: Interop Test Failure?
>
> Is the URL incorrect in this particular test?
>
> ConnectError: Connect failed to amqp:tcp:127.0.0.1:52652: Reconnect
> disabled
>
> Shouldn't the port be 5672 and not 52652?
>
> 
> From: Gordon Sim [g...@redhat.com]
> Sent: Tuesday, March 08, 2016 10:22 AM
> To: users@qpid.apache.org
> Subject: Re: QPID CPP 0.34: Interop Test Failure?
>
> On 08/03/16 15:43, Justin Ross wrote:
> > It means one of the tests defined here is failing:
> >
> >
> > https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_t
> > ests.py
> >
> > You should first determine which one is failing.  Use the following
> > command to run the test verbosely:
> >
> >ctest -R '^interop_tests$' -VV
> >
> > And then see what it says.
>
> You can also look under Testing/Temporary/LastTest.log under the build
> directory for a log of all the tests lasts run, which should have details of 
> the
> failing tests.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
> commands, e-mail: users-h...@qpid.apache.org
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
> commands, e-mail: users-h...@qpid.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: QPID CPP 0.34: Interop Test Failure?

[Steve Huston]

The tests try to pick an unused port, so 52652 is reasonable.

> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
> Sent: Tuesday, March 08, 2016 11:27 AM
> To: users@qpid.apache.org
> Subject: RE: QPID CPP 0.34: Interop Test Failure?
> 
> Is the URL incorrect in this particular test?
> 
> ConnectError: Connect failed to amqp:tcp:127.0.0.1:52652: Reconnect
> disabled
> 
> Shouldn't the port be 5672 and not 52652?
> 
> 
> From: Gordon Sim [g...@redhat.com]
> Sent: Tuesday, March 08, 2016 10:22 AM
> To: users@qpid.apache.org
> Subject: Re: QPID CPP 0.34: Interop Test Failure?
> 
> On 08/03/16 15:43, Justin Ross wrote:
> > It means one of the tests defined here is failing:
> >
> >
> > https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_t
> > ests.py
> >
> > You should first determine which one is failing.  Use the following
> > command to run the test verbosely:
> >
> >ctest -R '^interop_tests$' -VV
> >
> > And then see what it says.
> 
> You can also look under Testing/Temporary/LastTest.log under the build
> directory for a log of all the tests lasts run, which should have details of 
> the
> failing tests.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
> commands, e-mail: users-h...@qpid.apache.org
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
> commands, e-mail: users-h...@qpid.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: QPID CPP 0.34: Interop Test Failure?

[Flores, Paul A.]

Is the URL incorrect in this particular test?

ConnectError: Connect failed to amqp:tcp:127.0.0.1:52652: Reconnect disabled

Shouldn't the port be 5672 and not 52652?


From: Gordon Sim [g...@redhat.com]
Sent: Tuesday, March 08, 2016 10:22 AM
To: users@qpid.apache.org
Subject: Re: QPID CPP 0.34: Interop Test Failure?

On 08/03/16 15:43, Justin Ross wrote:
> It means one of the tests defined here is failing:
>
>
> https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_tests.py
>
> You should first determine which one is failing.  Use the following command
> to run the test verbosely:
>
>ctest -R '^interop_tests$' -VV
>
> And then see what it says.

You can also look under Testing/Temporary/LastTest.log under the build
directory for a log of all the tests lasts run, which should have
details of the failing tests.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID CPP 0.34: Interop Test Failure?

[Gordon Sim]

On 08/03/16 15:43, Justin Ross wrote:

It means one of the tests defined here is failing:


https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_tests.py

You should first determine which one is failing.  Use the following command
to run the test verbosely:

   ctest -R '^interop_tests$' -VV

And then see what it says.


You can also look under Testing/Temporary/LastTest.log under the build 
directory for a log of all the tests lasts run, which should have 
details of the failing tests.



-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID CPP 0.34: Interop Test Failure?

[Justin Ross]

It means one of the tests defined here is failing:


https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_tests.py

You should first determine which one is failing.  Use the following command
to run the test verbosely:

  ctest -R '^interop_tests$' -VV

And then see what it says.  Test failures are often environment dependent,
so the output may point out something you can change locally.  Or of course
it may be a real test failure.

https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/README.txt

Justin

On Tue, Mar 8, 2016 at 7:23 AM, Flores, Paul A. 
wrote:

> How do I resolve the single failing test; interop_test?
>
>
>
> More so what does this test failure mean?
>
>
>
> Any help is appreciated!
>