Hi, The NPE has gone from the proton-j, but we now are seeing "No address associated with hostname" and "Address already in use" errors when running the Python tests directly against proton-c.
I see the same results on my box RHEL 5.3 as Jenkins: See: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-c/48/console Thanks, Keith proton_tests.messenger.MessengerTest.testSendBogus ...................... fail Error during teardown: Traceback (most recent call last): File "./tests/python/proton-test", line 340, in run phase() File "/x1/jenkins/jenkins-slave/workspace/Qpid-proton-c/proton/tests/python/proton_tests/messenger.py", line 57, in teardown self.client.put(msg) File "/x1/jenkins/jenkins-slave/workspace/Qpid-proton-c/proton/proton-c/bindings/python/proton.py", line 388, in put self._check(pn_messenger_put(self._mng, message._msg)) File "/x1/jenkins/jenkins-slave/workspace/Qpid-proton-c/proton/proton-c/bindings/python/proton.py", line 228, in _check raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng))) MessengerException: [-2]: unable to connect to totally-bogus-address: getaddrinfo(totally-bogus-address, 5672): No address associated with hostname proton_tests.messenger.MessengerTest.testSendReceive .................... fail Error during setup: Traceback (most recent call last): File "./tests/python/proton-test", line 340, in run phase() File "/x1/jenkins/jenkins-slave/workspace/Qpid-proton-c/proton/tests/python/proton_tests/messenger.py", line 37, in setup self.server.subscribe("amqp://~0.0.0.0:12345") File "/x1/jenkins/jenkins-slave/workspace/Qpid-proton-c/proton/proton-c/bindings/python/proton.py", line 371, in subscribe self._check(PN_ERR) File "/x1/jenkins/jenkins-slave/workspace/Qpid-proton-c/proton/proton-c/bindings/python/proton.py", line 228, in _check raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng))) MessengerException: [-2]: unable to subscribe to address amqp://~0.0.0.0:12345: bind: Address already in use proton_tests.messenger.MessengerTest.testSendReceive100K ................ fail Error during setu On 23 March 2013 16:30, Rafael Schloming <r...@alum.mit.edu> wrote: > Should be fixed now. I accidentally checked that file in before it was > ready. > > --Rafael > > > On Sat, Mar 23, 2013 at 12:24 PM, Keith W <keith.w...@gmail.com> wrote: >> >> Hi, >> >> I'm seeing a NPE from MessengerTests since rev 1460174 whilst running >> the proton-j maven profile (mvn test -Pproton-j). >> >> It seems new test testDefaultRoute causes a NPE, and then the >> following MessengerTests fail with .java.net.BindException: Address >> already in use. >> >> The misleading commit message did mean I wasted time looking elsewhere >> before homing in on this commit. >> >> cheers, Keith >> >> >> proton_tests.messenger.MessengerTest.testDefaultRoute ................... >> fail >> Error during teardown: Traceback (most recent call last): >> File >> "/Users/keith/src/apache/qpid-proton/tests/target/classes/proton-test", >> line 340, in run >> phase() >> File >> "/Users/keith/src/apache/qpid-proton/tests/target/classes/proton_tests/messenger.py", >> line 57, in teardown >> self.client.put(msg) >> File "__pyclasspath__/proton.py", line 1061, in put >> NullPointerException: java.lang.NullPointerException >> proton_tests.messenger.MessengerTest.testDefaultRouteSubstitution >> .......java.net.BindException: Address already in use > >
