[jira] [Updated] (PROTON-831) proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5
[ https://issues.apache.org/jira/browse/PROTON-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated PROTON-831: -- Attachment: PROTON-831.patch proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5 - Key: PROTON-831 URL: https://issues.apache.org/jira/browse/PROTON-831 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.9 Environment: RHEL 5 Reporter: Irina Boverman Priority: Minor Attachments: PROTON-831.patch proton_tests.utils.SyncRequestResponseTest.test_request_response fail Error during test: Traceback (most recent call last): File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton-test, line 355, in run phase() File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton_tests/utils.py, line 92, in test_request_response test(foo) # Simple request/resposne File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton_tests/utils.py, line 82, in test response = client.call(Message(address=address, body=body)) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/utils.py, line 315, in call self.sender.send(request) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/utils.py, line 76, in send delivery = self.link.send(msg) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 2845, in send return obj.send(self, tag=tag) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 1098, in send dlv = sender.delivery(tag or sender.delivery_tag()) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 2858, in delivery_tag return next(self.tag_generator) NameError: global name 'next' is not defined Suggested fix (contributed by Ted Ross): Seems the next builtin function was introduced in Python 2.6. Perhaps this should be changed to: return self.tag_generator.next() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-831) proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5
[ https://issues.apache.org/jira/browse/PROTON-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340360#comment-14340360 ] Irina Boverman commented on PROTON-831: --- Added patch to resolve the issue. Rebuilt and ran tests, all passed 100%. proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5 - Key: PROTON-831 URL: https://issues.apache.org/jira/browse/PROTON-831 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.9 Environment: RHEL 5 Reporter: Irina Boverman Priority: Minor Attachments: PROTON-831.patch proton_tests.utils.SyncRequestResponseTest.test_request_response fail Error during test: Traceback (most recent call last): File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton-test, line 355, in run phase() File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton_tests/utils.py, line 92, in test_request_response test(foo) # Simple request/resposne File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton_tests/utils.py, line 82, in test response = client.call(Message(address=address, body=body)) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/utils.py, line 315, in call self.sender.send(request) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/utils.py, line 76, in send delivery = self.link.send(msg) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 2845, in send return obj.send(self, tag=tag) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 1098, in send dlv = sender.delivery(tag or sender.delivery_tag()) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 2858, in delivery_tag return next(self.tag_generator) NameError: global name 'next' is not defined Suggested fix (contributed by Ted Ross): Seems the next builtin function was introduced in Python 2.6. Perhaps this should be changed to: return self.tag_generator.next() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-831) proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5
Irina Boverman created PROTON-831: - Summary: proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5 Key: PROTON-831 URL: https://issues.apache.org/jira/browse/PROTON-831 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.9 Environment: RHEL 5 Reporter: Irina Boverman Priority: Minor proton_tests.utils.SyncRequestResponseTest.test_request_response fail Error during test: Traceback (most recent call last): File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton-test, line 355, in run phase() File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton_tests/utils.py, line 92, in test_request_response test(foo) # Simple request/resposne File /var/lib/jenkins/workspace/proton/label/rhel5-64/tests/python/proton_tests/utils.py, line 82, in test response = client.call(Message(address=address, body=body)) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/utils.py, line 315, in call self.sender.send(request) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/utils.py, line 76, in send delivery = self.link.send(msg) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 2845, in send return obj.send(self, tag=tag) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 1098, in send dlv = sender.delivery(tag or sender.delivery_tag()) File /var/lib/jenkins/workspace/proton/label/rhel5-64/proton-c/bindings/python/proton/__init__.py, line 2858, in delivery_tag return next(self.tag_generator) NameError: global name 'next' is not defined Suggested fix (contributed by Ted Ross): Seems the next builtin function was introduced in Python 2.6. Perhaps this should be changed to: return self.tag_generator.next() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-797) Can't complete build in F21
[ https://issues.apache.org/jira/browse/PROTON-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated PROTON-797: -- Description: git clone https://git-wip-us.apache.org/repos/asf/qpid-proton.git proton-master cmake -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_PREFIX=/usr -DSYSINSTALL_BINDINGS=ON -DBUILD_RUBY=OFF .. make all make docs ... /usr/bin/cmake -H/root/proton-master -B/root/proton-master/examples/engine/py --check-build-system CMakeFiles/Makefile.cmake 0 make -f CMakeFiles/Makefile2 docs make[1]: Entering directory '/root/proton-master/examples/engine/py' /usr/bin/cmake -H/root/proton-master -B/root/proton-master/examples/engine/py --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /root/proton-master/examples/engine/py/CMakeFiles 0 make -f CMakeFiles/Makefile2 proton-c/CMakeFiles/docs.dir/all make[2]: Entering directory '/root/proton-master/examples/engine/py' make -f proton-c/bindings/python/CMakeFiles/docs-py.dir/build.make proton-c/bindings/python/CMakeFiles/docs-py.dir/depend make[3]: Entering directory '/root/proton-master/examples/engine/py' cd /root/proton-master/examples/engine/py /usr/bin/cmake -E cmake_depends Unix Makefiles /root/proton-master /root/proton-master/proton-c/bindings/python /root/proton-master/examples/engine/py /root/proton-master/examples/engine/py/proton-c/bindings/python /root/proton-master/examples/engine/py/proton-c/bindings/python/CMakeFiles/docs-py.dir/DependInfo.cmake --color= Scanning dependencies of target docs-py make[3]: Leaving directory '/root/proton-master/examples/engine/py' make -f proton-c/bindings/python/CMakeFiles/docs-py.dir/build.make proton-c/bindings/python/CMakeFiles/docs-py.dir/build make[3]: Entering directory '/root/proton-master/examples/engine/py' cd /root/proton-master/examples/engine/py/proton-c/bindings/python /usr/bin/python /root/proton-master/proton-c/bindings/python/../../env.py -- PYTHONPATH=/root/proton-master/examples/engine/py/proton-c/bindings/python:/root/proton-master/proton-c/bindings/python /usr/bin/epydoc -v --no-private --html -o /root/proton-master/examples/engine/py/proton-c/bindings/python/html /root/proton-master/proton-c/bindings/python/proton/__init__.py proton/handlers.py proton/reactors.py proton/utils.py proton/wrapper.py Error: Could not find a file or object named proton/handlers.py Error: Could not find a file or object named proton/reactors.py Error: Could not find a file or object named proton/utils.py Error: Could not find a file or object named proton/wrapper.py + | File /root/proton-master/proton-c/bindings/python/proton/__init__.py, line 3632, in proton.Url | Warning: Line 3635: Improper paragraph indentation. | make[3]: Leaving directory '/root/proton-master/examples/engine/py' was: git clone git://git.app.eng.bos.redhat.com/rh-qpid-proton.git proton-master cmake -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_PREFIX=/usr -DSYSINSTALL_BINDINGS=ON -DBUILD_RUBY=OFF .. make all make docs ... /usr/bin/cmake -H/root/proton-master -B/root/proton-master/examples/engine/py --check-build-system CMakeFiles/Makefile.cmake 0 make -f CMakeFiles/Makefile2 docs make[1]: Entering directory '/root/proton-master/examples/engine/py' /usr/bin/cmake -H/root/proton-master -B/root/proton-master/examples/engine/py --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /root/proton-master/examples/engine/py/CMakeFiles 0 make -f CMakeFiles/Makefile2 proton-c/CMakeFiles/docs.dir/all make[2]: Entering directory '/root/proton-master/examples/engine/py' make -f proton-c/bindings/python/CMakeFiles/docs-py.dir/build.make proton-c/bindings/python/CMakeFiles/docs-py.dir/depend make[3]: Entering directory '/root/proton-master/examples/engine/py' cd /root/proton-master/examples/engine/py /usr/bin/cmake -E cmake_depends Unix Makefiles /root/proton-master /root/proton-master/proton-c/bindings/python /root/proton-master/examples/engine/py /root/proton-master/examples/engine/py/proton-c/bindings/python /root/proton-master/examples/engine/py/proton-c/bindings/python/CMakeFiles/docs-py.dir/DependInfo.cmake --color= Scanning dependencies of target docs-py make[3]: Leaving directory '/root/proton-master/examples/engine/py' make -f proton-c/bindings/python/CMakeFiles/docs-py.dir/build.make proton-c/bindings/python/CMakeFiles/docs-py.dir/build make[3]: Entering directory '/root/proton-master/examples/engine/py' cd /root/proton-master/examples/engine/py/proton-c/bindings/python /usr/bin/python /root/proton-master/proton-c/bindings/python/../../env.py --
[jira] [Created] (PROTON-779) RHEL 7 Build Issue
Irina Boverman created PROTON-779: - Summary: RHEL 7 Build Issue Key: PROTON-779 URL: https://issues.apache.org/jira/browse/PROTON-779 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9 Environment: RHEL 7 Reporter: Irina Boverman cmake -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_SHARED_LINKER_FLAGS=-Wl,-z,relro -DCMAKE_INSTALL_PREFIX=/usr -DSYSINSTALL_BINDINGS=ON -DBUILD_RUBY=OFF .. make all docs Results in this: Built target docs-c make -f proton-c/bindings/python/CMakeFiles/docs-py.dir/build.make proton-c/bindings/python/CMakeFiles/docs-py.dir/depend make[3]: Entering directory `/var/lib/jenkins/workspace/proton/label/rhel7-64/build' cd /var/lib/jenkins/workspace/proton/label/rhel7-64/build /usr/bin/cmake -E cmake_depends Unix Makefiles /var/lib/jenkins/workspace/proton/label/rhel7-64 /var/lib/jenkins/workspace/proton/label/rhel7-64/proton-c/bindings/python /var/lib/jenkins/workspace/proton/label/rhel7-64/build /var/lib/jenkins/workspace/proton/label/rhel7-64/build/proton-c/bindings/python /var/lib/jenkins/workspace/proton/label/rhel7-64/build/proton-c/bindings/python/CMakeFiles/docs-py.dir/DependInfo.cmake --color= Scanning dependencies of target docs-py make[3]: Leaving directory `/var/lib/jenkins/workspace/proton/label/rhel7-64/build' make -f proton-c/bindings/python/CMakeFiles/docs-py.dir/build.make proton-c/bindings/python/CMakeFiles/docs-py.dir/build make[3]: Entering directory `/var/lib/jenkins/workspace/proton/label/rhel7-64/build' cd /var/lib/jenkins/workspace/proton/label/rhel7-64/build/proton-c/bindings/python /usr/bin/python /var/lib/jenkins/workspace/proton/label/rhel7-64/proton-c/bindings/python/../../env.py -- PYTHONPATH=/var/lib/jenkins/workspace/proton/label/rhel7-64/build/proton-c/bindings/python:/var/lib/jenkins/workspace/proton/label/rhel7-64/proton-c/bindings/python /usr/bin/epydoc -v --no-private --html -o /var/lib/jenkins/workspace/proton/label/rhel7-64/build/proton-c/bindings/python/html /var/lib/jenkins/workspace/proton/label/rhel7-64/proton-c/bindings/python/proton.py Error: Could not find a file or object named /var/lib/jenkins/ workspace/proton/label/rhel7-64/proton-c/bindings/python/ proton.py Error: Nothing left to document! make[3]: *** [proton-c/bindings/python/CMakeFiles/docs-py] Error 1 make[3]: Leaving directory `/var/lib/jenkins/workspace/proton/label/rhel7-64/build' make[2]: *** [proton-c/bindings/python/CMakeFiles/docs-py.dir/all] Error 2 make[2]: Leaving directory `/var/lib/jenkins/workspace/proton/label/rhel7-64/build' make[1]: *** [proton-c/CMakeFiles/docs.dir/rule] Error 2 make[1]: Leaving directory `/var/lib/jenkins/workspace/proton/label/rhel7-64/build' make: *** [docs] Error 2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-780) RHEL 6 CXX Build Issue
Irina Boverman created PROTON-780: - Summary: RHEL 6 CXX Build Issue Key: PROTON-780 URL: https://issues.apache.org/jira/browse/PROTON-780 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.9 Environment: RHEL 6, CXX Compiler Reporter: Irina Boverman mkdir -p build cd build cmake -DBUILD_WITH_CXX=ON .. make Results in this: 20%] Building CXX object proton-c/CMakeFiles/qpid-proton.dir/src/log.c.o In file included from /home/jenkins/workspace/proton-cxx/label/master/proton-c/src/log.c:20: /home/jenkins/workspace/proton-cxx/label/master/proton-c/include/proton/log.h:54:17: error: anonymous variadic macros were introduced in C99 make[2]: *** [proton-c/CMakeFiles/qpid-proton.dir/src/log.c.o] Error 1 make[1]: *** [proton-c/CMakeFiles/qpid-proton.dir/all] Error 2 make: *** [all] Error 2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-521) Replace proton-project with proton in maven related build files
Irina Boverman created PROTON-521: - Summary: Replace proton-project with proton in maven related build files Key: PROTON-521 URL: https://issues.apache.org/jira/browse/PROTON-521 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.6 Reporter: Irina Boverman Priority: Trivial Fix For: 0.7 This change makes it easier to build downstream products. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (PROTON-521) Replace proton-project with proton in maven related build files
[ https://issues.apache.org/jira/browse/PROTON-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated PROTON-521: -- Attachment: replace-proton-project.txt Attached patch will resolve this issue. Replace proton-project with proton in maven related build files --- Key: PROTON-521 URL: https://issues.apache.org/jira/browse/PROTON-521 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.6 Reporter: Irina Boverman Priority: Trivial Fix For: 0.7 Attachments: replace-proton-project.txt This change makes it easier to build downstream products. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (PROTON-250) Add -fvisibility option when building shared libraries
[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated PROTON-250: -- Attachment: (was: patch.txt) Add -fvisibility option when building shared libraries --- Key: PROTON-250 URL: https://issues.apache.org/jira/browse/PROTON-250 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.3 Environment: GNU Compiler Reporter: Irina Boverman Priority: Minor Attachments: proton.patch Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility Attached patch (patch.txt) will build libqpid-proton.so shared library using this flag. It reduces number of symbols from 700+ to 500+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-250) Add -fvisibility option when building shared libraries
[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated PROTON-250: -- Attachment: proton.patch Add -fvisibility option when building shared libraries --- Key: PROTON-250 URL: https://issues.apache.org/jira/browse/PROTON-250 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.3 Environment: GNU Compiler Reporter: Irina Boverman Priority: Minor Attachments: proton.patch Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility Attached patch (patch.txt) will build libqpid-proton.so shared library using this flag. It reduces number of symbols from 700+ to 500+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-250) Add -fvisibility option when building shared libraries
Irina Boverman created PROTON-250: - Summary: Add -fvisibility option when building shared libraries Key: PROTON-250 URL: https://issues.apache.org/jira/browse/PROTON-250 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.3 Environment: GNU Compiler Reporter: Irina Boverman Priority: Minor Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-250) Add -fvisibility option when building shared libraries
[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated PROTON-250: -- Description: Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility Attached patch (patch.txt) will build libqpid-proton.so shared library using this flag. It reduces number of symbols from 700+ to 500+. was: Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility Add -fvisibility option when building shared libraries --- Key: PROTON-250 URL: https://issues.apache.org/jira/browse/PROTON-250 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.3 Environment: GNU Compiler Reporter: Irina Boverman Priority: Minor Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility Attached patch (patch.txt) will build libqpid-proton.so shared library using this flag. It reduces number of symbols from 700+ to 500+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
