Hello, I tried to launch proton 0.12.0 unit tests on Linux, everything is working fine except when i launch SASL related unit tests in python-test.
The following 2 tests are failing when SASL is activated but are passing when SASL is deactivated: proton_tests.engine.SaslEventTest.testPipelinedServerReadFirst: File "/data/src/new/proton-ssl/qpid-proton/tests/python/proton_tests/engine.py", line 2679, in testPipelinedServerReadFirst assert server.sasl().outcome == SASL.OK AssertionError proton_tests.engine.SaslEventTest.testPipelinedServerWriteFirst: File "/data/src/new/proton-ssl/qpid-proton/tests/python/proton_tests/engine.py", line 2288, in expect_oneof assert False, "actual events %s did not match any of the expected sequences: %s" % (events, sequences) AssertionError: actual events [PN_CONNECTION_INIT(<proton.Connection 0x7fcafa7766d0 ~ 0x1123220>), PN_CONNECTION_BOUND(<proton.Connection 0x7fcafa7766d0 ~ 0x1123220>), PN_TRANSPORT_ERROR(<proton.Transport 0x7fcafa7766d0 ~ 0x1153590>), PN_TRANSPORT_TAIL_CLOSED(<proton.Transport 0x7fcafa7766d0 ~ 0x1153590>), PN_TRANSPORT_HEAD_CLOSED(<proton.Transport 0x7fcafa7766d0 ~ 0x1153590>), PN_TRANSPORT_CLOSED(<proton.Transport 0x7fcafa7766d0 ~ 0x1153590>)] did not match any of the expected sequences: ((PN_CONNECTION_INIT, PN_CONNECTION_BOUND, PN_TRANSPORT),) The following test is only launched when SASL is activated and is blocking: test_authentication_via_container_attributes: 2016-06-01 12:11:18,077 ERROR amqp:unauthorized-access: Authentication failed [mech=(null)] 2016-06-01 12:11:18,078 ERROR amqp:connection:framing-error: connection aborted Has anyone already encountered those failures? Thanks, Rabih
