On 21 April 2015 at 12:52, Rafael Schloming <[email protected]> wrote: > I'm seeing a couple of issues with the recently landed sasl changes. I'm > getting four test failures in the python tests (see details at the end). > I'm also seeing interop issues with the proton.js built prior to these > changes, and with these changes in place the javascript build seems to be > messed up (not finding new symbols). > > Is anyone else seeing similar issues? > > --Rafael > > proton_tests.sasl.SaslTest.testPipelined2 > ........................................ fail > Error during test: Traceback (most recent call last): > File "/home/rhs/proton/tests/python/proton-test", line 355, in run > phase() > File "/home/rhs/proton/tests/python/proton_tests/sasl.py", line 161, in > testPipelined2 > assert len(out1) > 0 > AssertionError > proton_tests.sasl.SaslTest.testPipelinedClient > ................................... fail > Error during test: Traceback (most recent call last): > File "/home/rhs/proton/tests/python/proton-test", line 355, in run > phase() > File "/home/rhs/proton/tests/python/proton_tests/sasl.py", line 68, in > testPipelinedClient > assert self.s1.outcome == SASL.OK > AssertionError > proton_tests.sasl.SaslTest.testPipelinedClientFail > ............................... fail > Error during test: Traceback (most recent call last): > File "/home/rhs/proton/tests/python/proton-test", line 355, in run > phase() > File "/home/rhs/proton/tests/python/proton_tests/sasl.py", line 95, in > testPipelinedClientFail > assert self.s1.outcome == SASL.AUTH > AssertionError > proton_tests.sasl.SaslTest.testSaslAndAmqpInSingleChunk > .......................... fail > Error during test: Traceback (most recent call last): > File "/home/rhs/proton/tests/python/proton-test", line 355, in run > phase() > File "/home/rhs/proton/tests/python/proton_tests/sasl.py", line 140, in > testSaslAndAmqpInSingleChunk > assert self.s2.outcome == SASL.OK > AssertionError
I dont have the javascript bits building, but the python tests are all passing for me. I updated, used git clean to do a clean up, then did a fresh build. Snippet of the SASL tests from "ctest -V -R python-test": 2: proton_tests.sasl.SaslTest.testFracturedSASL ............................ pass 2: proton_tests.sasl.SaslTest.testPipelined2 ............................... pass 2: [0x4e009d0]:Authenticated user: anonymous with mechanism ANONYMOUS 2: proton_tests.sasl.SaslTest.testPipelinedClient .......................... pass 2: [0x4e03f10]:sasl error: SASL(-1): generic failure: Client mechanism not in mechanism inclusion list. 2: proton_tests.sasl.SaslTest.testPipelinedClientFail ...................... pass 2: [0x4e054c0]:Authenticated user: anonymous with mechanism ANONYMOUS 2: proton_tests.sasl.SaslTest.testSaslAndAmqpInSingleChunk ................. pass 2: proton_tests.sasl.SaslTest.testSaslSkipped .............................. pass 2: proton_tests.sasl.SaslTest.testSaslSkippedFail .......................... pass 2: proton_tests.sasl.SaslTest.test_singleton ............................... pass The only bit I wonder about (wihtout bothing to look further) is the 'generic failure' message in the middle.
