[
https://issues.apache.org/jira/browse/PROTON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1723:
--------------------------------
Fix Version/s: (was: proton-c-0.20.0)
proton-c-0.21.0
> [proton-c] Building with sasl2-bin not installed results in test failure
> ------------------------------------------------------------------------
>
> Key: PROTON-1723
> URL: https://issues.apache.org/jira/browse/PROTON-1723
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Environment: Linux Mint 18.2
> Reporter: Timothy Bish
> Assignee: Justin Ross
> Priority: Trivial
> Fix For: proton-c-0.21.0
>
>
> Building the latest upstream code and running the tests results in a failed
> test "ruby-test-container" on my Ubuntu based machine. The INSTALL.md omits
> the need to install "sasl2-bin" which leads to the test failure. The install
> guide needs an update but also the test might be made to check for that an
> maybe offer a better diagnostic or just not run on platforms that are missing
> the required dependencies for that test.
> {noformat}
> timothy@OfficePC ~/temp/0.20.0/qpid-proton-0.19.0/build $ ctest -V -R
> ruby-test-container
> UpdateCTestConfiguration from
> :/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/DartConfiguration.tcl
> Parse Config
> file:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/DartConfiguration.tcl
> UpdateCTestConfiguration from
> :/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/DartConfiguration.tcl
> Parse Config
> file:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/DartConfiguration.tcl
> Test project /home/timothy/temp/0.20.0/qpid-proton-0.19.0/build
> Constructing a list of tests
> Done constructing a list of tests
> Checking test dependency graph...
> Checking test dependency graph end
> test 18
> Start 18: ruby-test-container
>
> 18: Test command: /usr/bin/python
> "/home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/env.py" "--"
> "PATH=/home/timothy/.local/bin:/home/timothy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/proton-c/bindings/ruby:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/proton-c"
>
> "RUBYLIB=:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/lib:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/spec:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/proton-c/bindings/ruby:/home/timothy/temp/0.20.0/qpid-proton-0.19.0/build/proton-c"
> "SASLPASSWD=SASLPASSWD_EXE-NOTFOUND" "RUBYOPT=-W0" "/usr/bin/ruby"
> "/home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb"
> "-v"
> 18: Test timeout computed to be: 1500
> 18: sh: 1: SASLPASSWD_EXE-NOTFOUND: not found
> 18:
> /home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb:282:in
> `make_user': undefined local variable or method `makepw_cmd' for
> #<ContainerSASLTest::SASLConfig:0x0000000202ec00> (NameError)
> 18: from
> /home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb:261:in
> `initialize'
> 18: from
> /home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb:284:in
> `new'
> 18: from
> /home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb:284:in
> `<class:SASLConfig>'
> 18: from
> /home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb:249:in
> `<class:ContainerSASLTest>'
> 18: from
> /home/timothy/temp/0.20.0/qpid-proton-0.19.0/proton-c/bindings/ruby/tests/test_container.rb:221:in
> `<main>'
> 1/1 Test #18: ruby-test-container ..............***Failed 0.08 sec
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
