Ken Giusti created PROTON-1612:
----------------------------------

             Summary: python test fail if Cyrus SASL PLAIN and MD5 packages not 
installed
                 Key: PROTON-1612
                 URL: https://issues.apache.org/jira/browse/PROTON-1612
             Project: Qpid Proton
          Issue Type: Bug
          Components: proton-c, python-binding
    Affects Versions: proton-c-0.18.0
         Environment: clean centos 7 docker container
            Reporter: Ken Giusti
             Fix For: proton-c-0.18.0


After following the directions in INSTALL.md, and installing the Python build 
tools (python-devel), the python-test unit test fails the SASL tests.

1: proton_tests.sasl.SASLMechTest.testDIGESTMD5 ............................ 
fail
1: Error during test:  Traceback (most recent call last):
1:     File "/root/qpid-proton-0.18.0-beta/tests/python/proton-test", line 365, 
in run
1:       phase()
1:     File "/root/qpid-proton-0.18.0-beta/tests/python/proton_tests/sasl.py", 
line 326, in testDIGESTMD5
1:       _testSaslMech(self, 'DIGEST-MD5')
1:     File "/root/qpid-proton-0.18.0-beta/tests/python/proton_tests/sasl.py", 
line 53, in _testSaslMech
1:       assert self.t2.authenticated == authenticated, authenticated
1:   AssertionError: True

proton_tests.reactor.ContainerTest.test_authentication_via_url .......... fail
....
1:     File 
"/root/qpid-proton-0.18.0-beta/tests/python/proton_tests/reactor.py", line 339, 
in on_connection_opening
1:       assert event.connection.transport.user == "user@proton"
1:   AssertionError



These tests require MD5 and PLAIN support.  The following packages must be 
installed for the tests to pass:

$ yum install cyrus-sasl-plain cyrus-sasl-md5

Either these packages must be listed as required in the INSTALL.md file, or the 
tests should skip if these mechanisms are not available.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to