[
https://issues.apache.org/jira/browse/PROTON-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021566#comment-17021566
]
Jiri Daněk edited comment on PROTON-2167 at 1/22/20 10:56 PM:
--------------------------------------------------------------
Saw a weird failure when upgrading macOS version. The Travis job is on Linux,
so it is unrelated to mac, and it is probably unreproducible, so I'll just post
that Valgrind crash here
It's from a coverage build on Ubuntu Trusty (I'm a bit surprised that coverage
build is running tests under Valgrind)
edit: it is not coverage build, I made a typo so -DCMAKE_BUILD_TYPE=Coverage
was not set.
{noformat}
26: proton_tests.ssl.SslTest.test_server_authentication .....................
pass
26: proton_tests.ssl.SslTest.test_server_authentication_messenger_app .......
26: vex: the `impossible' happened:
26: isZeroU
26: vex storage: T total 418446632 bytes allocated
26: vex storage: P total 640 bytes allocated
26:
26: valgrind: the 'impossible' happened:
26: LibVEX called failure_exit().
26:
26: host stacktrace:
26: ==12154== at 0x38083F48: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38084064: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380842A1: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380842CA: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3809F682: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38145428: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3815256D: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38156692: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x381572C6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38159188: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3815A1D6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3814320C: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380A1C0B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26:
26: sched status:
26: running_tid=1
26:
26: Thread 1: status = VgTs_Runnable (lwpid 12154)
26: ==12154== at 0x59D44C0: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x59B313F: EC_POINT_mul (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x73850F3D8CCB7EFF: ???
26: ==12154== by 0x62DB8CF: ???
26: ==12154== by 0x59BAEA7: d2i_ECPrivateKey (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x59BF4C0: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x5A0A118: EVP_PKCS82PKEY (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x5A30634: PEM_read_bio_PrivateKey (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x54A36E7: SSL_CTX_use_PrivateKey_file (in
/lib/x86_64-linux-gnu/libssl.so.1.0.0)
26: ==12154== by 0x4E72C74: pn_ssl_domain_set_credentials (openssl.c:604)
26: ==12154== by 0x4E508EF: pn_listener_ctx.lto_priv.109 (messenger.c:396)
26: ==12154== by 0x4E70543: pn_messenger_subscribe_ttl (messenger.c:1826)
26: ==12154== by 0x401B3C: main (msgr-recv.c:207)
26:
26:
26: Note: see also the FAQ in the source distribution.
26: It contains workarounds to several common problems.
26: In particular, if Valgrind aborted or crashed after
26: identifying problems in your program, there's a good chance
26: that fixing those problems will prevent Valgrind aborting or
26: crashing, especially if it happened in m_mallocfree.c.
26:
26: If that doesn't help, please report this bug to: www.valgrind.org
26:
26: In the bug report, send all the above text, the valgrind
26: version, and what OS and version you are using. Thanks.
26:
26: fail
26: Error during test: Traceback (most recent call last):
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/main.py",
line 363, in run
26: phase()
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/ssl.py",
line 871, in test_server_authentication_messenger_app
26: receiver.start()
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/common.py",
line 296, in start
26: self._ready() # wait for it to initialize
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/common.py",
line 465, in _ready
26: assert r.strip() == "READY", "Unexpected input while waiting for
receiver to initialize: %s" % r
26: AssertionError: Unexpected input while waiting for receiver to initialize:
26: proton_tests.ssl.SslTest.test_server_certificate ........................
pass
{noformat}
https://api.travis-ci.org/v3/job/640589363/log.txt
was (Author: jdanek):
Saw a weird failure when upgrading macOS version. The Travis job is on Linux,
so it is unrelated to mac, and it is probably unreproducible, so I'll just post
that Valgrind crash here
It's from a coverage build on Ubuntu Trusty (I'm a bit surprised that coverage
build is running tests under Valgrind)
{noformat}
26: proton_tests.ssl.SslTest.test_server_authentication .....................
pass
26: proton_tests.ssl.SslTest.test_server_authentication_messenger_app .......
26: vex: the `impossible' happened:
26: isZeroU
26: vex storage: T total 418446632 bytes allocated
26: vex storage: P total 640 bytes allocated
26:
26: valgrind: the 'impossible' happened:
26: LibVEX called failure_exit().
26:
26: host stacktrace:
26: ==12154== at 0x38083F48: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38084064: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380842A1: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380842CA: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3809F682: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38145428: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3815256D: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38156692: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x381572C6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x38159188: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3815A1D6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x3814320C: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380A1C0B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26: ==12154== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
26:
26: sched status:
26: running_tid=1
26:
26: Thread 1: status = VgTs_Runnable (lwpid 12154)
26: ==12154== at 0x59D44C0: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x59B313F: EC_POINT_mul (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x73850F3D8CCB7EFF: ???
26: ==12154== by 0x62DB8CF: ???
26: ==12154== by 0x59BAEA7: d2i_ECPrivateKey (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x59BF4C0: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x5A0A118: EVP_PKCS82PKEY (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x5A30634: PEM_read_bio_PrivateKey (in
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
26: ==12154== by 0x54A36E7: SSL_CTX_use_PrivateKey_file (in
/lib/x86_64-linux-gnu/libssl.so.1.0.0)
26: ==12154== by 0x4E72C74: pn_ssl_domain_set_credentials (openssl.c:604)
26: ==12154== by 0x4E508EF: pn_listener_ctx.lto_priv.109 (messenger.c:396)
26: ==12154== by 0x4E70543: pn_messenger_subscribe_ttl (messenger.c:1826)
26: ==12154== by 0x401B3C: main (msgr-recv.c:207)
26:
26:
26: Note: see also the FAQ in the source distribution.
26: It contains workarounds to several common problems.
26: In particular, if Valgrind aborted or crashed after
26: identifying problems in your program, there's a good chance
26: that fixing those problems will prevent Valgrind aborting or
26: crashing, especially if it happened in m_mallocfree.c.
26:
26: If that doesn't help, please report this bug to: www.valgrind.org
26:
26: In the bug report, send all the above text, the valgrind
26: version, and what OS and version you are using. Thanks.
26:
26: fail
26: Error during test: Traceback (most recent call last):
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/main.py",
line 363, in run
26: phase()
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/ssl.py",
line 871, in test_server_authentication_messenger_app
26: receiver.start()
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/common.py",
line 296, in start
26: self._ready() # wait for it to initialize
26: File
"/home/travis/build/jdanekrh/qpid-proton/python/tests/proton_tests/common.py",
line 465, in _ready
26: assert r.strip() == "READY", "Unexpected input while waiting for
receiver to initialize: %s" % r
26: AssertionError: Unexpected input while waiting for receiver to initialize:
26: proton_tests.ssl.SslTest.test_server_certificate ........................
pass
{noformat}
https://api.travis-ci.org/v3/job/640589363/log.txt
> Travis build on macOS 10.12 fails on ruby and openssl library issues
> --------------------------------------------------------------------
>
> Key: PROTON-2167
> URL: https://issues.apache.org/jira/browse/PROTON-2167
> Project: Qpid Proton
> Issue Type: Test
> Components: ruby-binding
> Reporter: Jiri Daněk
> Assignee: Alan Conway
> Priority: Major
>
> {noformat}
> $ gem install minitest
> Error loading RubyGems plugin
> "/Users/travis/.rvm/gems/ruby-2.4.2@global/gems/executable-hooks-1.3.2/lib/rubygems_plugin.rb":
>
> dlopen(/Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle,
> 9): Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
> Referenced from:
> /Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle
> Reason: image not found -
> /Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle
> (LoadError)
> Error loading RubyGems plugin
> "/Users/travis/.rvm/gems/ruby-2.4.2/gems/gem-wrappers-1.4.0/lib/rubygems_plugin.rb":
>
> dlopen(/Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle,
> 9): Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
> Referenced from:
> /Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle
> Reason: image not found -
> /Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle
> (LoadError)
> ERROR: Loading command: install (LoadError)
>
> dlopen(/Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle,
> 9): Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
> Referenced from:
> /Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle
> Reason: image not found -
> /Users/travis/.rvm/gems/ruby-2.4.2/gems/openssl-2.0.6/lib/openssl.bundle
> ERROR: While executing gem ... (NoMethodError)
> undefined method `invoke_with_build_args' for nil:NilClass
> The command "gem install minitest" failed and exited with 1 during .
> {noformat}
> https://travis-ci.org/apache/qpid-proton/jobs/638630148
> I tried a few things yesterday (reinstall ruby from brew, reinstall using
> rvm), but could not get past this.
> Could we maybe drop osx 10.12 and test/support only newer versions?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
