I just ran a maven-only clean build locally with no problems. You should have PN_MILLIS_MAX defined in proton-j/src/main/resources/ctypes.py, and this should be imported from proton-j/src/main/resources/cproton.py. Can you verify that this is as expected?
--Rafael On Mon, Jul 6, 2015 at 5:50 AM, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > The recent changes on Proton-J seemed to have created some issues: > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/1032/console > > The module currently requries Java 7 to compile, which is a slightly > out of sync with the compiler source+target still being set to Java 6 > (which the above job is using). > > Once using Java 8 to do the maven build locally, the python tests then > failed with: > > proton_tests.utils.SyncRequestResponseTest.test_request_response ........ > fail > Error during test: Traceback (most recent call last): > File "/home/gemmellr/workspace/proton/tests/python/proton-test", > line 360, in run > phase() > File > "/home/gemmellr/workspace/proton/tests/python/proton_tests/utils.py", > line 89, in test_request_response > connection = BlockingConnection(server.url, timeout=self.timeout) > File > "/home/gemmellr/workspace/proton/tests/../proton-c/bindings/python/proton/utils.py", > line 195, in __init__ > self.wait(lambda: not (self.conn.state & Endpoint.REMOTE_UNINIT), > File > "/home/gemmellr/workspace/proton/tests/../proton-c/bindings/python/proton/utils.py", > line 229, in wait > container_timeout = self.container.timeout > File > "/home/gemmellr/workspace/proton/tests/../proton-c/bindings/python/proton/reactor.py", > line 104, in _get_timeout > return millis2timeout(pn_reactor_get_timeout(self._impl)) > File > "/home/gemmellr/workspace/proton/tests/../proton-c/bindings/python/proton/__init__.py", > line 2337, in millis2timeout > if millis == PN_MILLIS_MAX: return None > NameError: global name 'PN_MILLIS_MAX' is not defined > > I notice that the TravisCI job did pass: > https://travis-ci.org/apache/qpid-proton/builds/69665060 > > I guess the main difference is it ran via cmake so the proton-c build > was performed before the proton-j tests were run. > > Robbie >
