On 20/02/16 20:48, Morgan Lindqvist wrote:
Test 6,7,8 (same massage for all three)
Here my guess is that the test is supposed to give an exception but that it
happens in the wrong place and is interpreted as a correct exception. Am I
correct in this?
-------------------------------------------------------------------
Failed: Exception - Link failed to create User 127.0.0.1@QPID federation
connection denied. Systems with authentication enabled must specify ACL
create link rules.
(/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/qpid/broker/ConnectionHandler.cpp:259)
<end of output>
Test time = 14.65 sec
Test Passed.
"sasl_fed_ex_link" end time: Feb 20 20:27 CET
"sasl_fed_ex_link" time elapsed: 00:00:14
--------------------------------------------------------------------------
This looks like it is an issue with the test. My guess is that the
requirement to have an explicit acl came after the test was added, and
as the test appears to pass, it was never updated accordingly.
Not sure exactly why the test is not signalling a failure, but I see
this same error too now you point it out.
Test 18)
All sub-tests of test 18 is successful except for the following one.
++++++++++++++++++++++++++++++++++++++++++++++++++
qpid.tests.messaging.endpoints.SetupTests.testConnectError ..............
fail
Error during test: Traceback (most recent call last):
File
"/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/build/src/tests/python/commands/qpid-python-test",
line 340, in run
phase()
File
"/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/build/src/tests/python/qpid/tests/messaging/endpoints.py",
line 59, in testConnectErro
r
assert "refused" in str(e)
AssertionError
++++++++++++++++++++++++++++++++++++++++++++++++++
This is a strange one. The connection attempt is failing as expected,
but the error message isn't as expected. Can you run the attached python
script and see what error is reported? I doubt this is too much of a
concern, but would be nice to understand and fix.
Test 20)
This sub-test fails and then the rest fails with a reconnect disabled
message, so I guess if the first one is fixed the remaining one might be as
well.
==================================================
interop_tests.CppTxTest.test_txtest2 ....................................
fail
Error during test: Traceback (most recent call last):
File
"/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/build/src/tests/python/commands/qpid-python-test",
line 340, in run
phase()
File
"/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/tests/interop_tests.py", line
173, in test_txtest2
self.popen(["qpid-txtest2"] + self.connect_opts).assert_exit_ok()
File "/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/tests/brokertest.py",
line 223, in assert_exit_ok
if self.wait() != 0: self.unexpected("Exit code %d" % self.returncode)
File "/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/tests/brokertest.py",
line 181, in unexpected
raise BadProcessStatus("%s %s%s" % (self.pname, msg, err))
BadProcessStatus: qpid-txtest2-2 Exit code 2:
qpid-txtest2: Transfer agents failed
============================================
That sounds like the broker is crashing. The simplest way to debug this
perhaps is to start a broker and then run ./src/tests/qpid-txtest from
the cpp build directory. (That is essentially what this test is doing,
but this way we can see more clearly what is happening).
Test 21)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
ha_tests.TransactionTests.test_other_tx_tests ...........................
fail
Error during test: Traceback (most recent call last):
File
"/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/build/src/tests/python/commands/qpid-python-test",
line 340, in run
phase()
File "/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/tests/ha_tests.py",
line 1620, in test_other_tx_tests
"*.tx.*"], stdout=None, stderr=None).assert_exit_ok()
File "/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/tests/brokertest.py",
line 223, in assert_exit_ok
if self.wait() != 0: self.unexpected("Exit code %d" % self.returncode)
File "/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/src/tests/brokertest.py",
line 181, in unexpected
raise BadProcessStatus("%s %s%s" % (self.pname, msg, err))
BadProcessStatus: qpid-python-test-154 Exit code 1
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
My guess is that this one is similar to the one below. I.e. it can't
find the tests module.
Test 25)
Do I need to do something special to get AMQP 1.0 activated or working? It
is AMQP 1.0 that I will use in the end.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Traceback (most recent call last):
File
"/home/webrtc/NordicWay-1.0/qpid-cpp-0.34/build/src/tests/python/commands/qpid-python-test",
line 563, in <module>
m = __import__(name, None, None, ["dummy"])
ImportError: No module named broker_1_0
FAIL swigged python tests:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
There are some tests of various aspects of broker behaviour written in
python that are bundled as a separate package. The test can't find these
and is failing as a result (possibly should just skip). If you want to
install them, it is the qpid-tests-0.32.tar.gz tarball (I should have
mentioned these in my earlier mail, sorry!).
from qpid.messaging import Connection, ConnectError
try:
conn = Connection.establish("localhost:4")
print "connect succeeded"
except ConnectError, e:
print e
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
