Hi Jiri, Thanks for your patience. There are errors in tests even then. Here's a failed log
Send first then receive 11: ---------------------------------------------------------------------- 11: Traceback (most recent call last): 11: File "testme", line 52, in test_send_receive 11: with Broker() as b: 11: File "testme", line 38, in __init__ 11: super(Broker, self).__init__(["broker", "", "0"], kill_me=True) 11: File "/path/to/qpid-proton/tests/py/test_subprocess.py", line 121, in __init__ 11: super(Server, self).__init__(*args, **kwargs) 11: File "/path/to/qpid-proton/tests/py/test_subprocess.py", line 65, in __init__ 11: super(Popen, self).__init__(*args, **kwargs) 11: File "/usr/lib/python2.7/subprocess.py", line 394, in __init__ 11: errread, errwrite) 11: File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child 11: raise child_exception 11: OSError: [Errno 2] No such file or directory Regards, Kajal On Thu, Apr 1, 2021 at 5:23 PM Jiri Daněk <jda...@redhat.com> wrote: > On Thu, Apr 1, 2021 at 1:20 PM Kajal Sah <kajalksa...@gmail.com> wrote: > > > Thanks, Jiri. Now, I am able to see why tests are failing. It is probably > > because of missing ruby packages. > > > > Here is the error log > > > > > > /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in > > `require': libsasl2.so.3: cannot open shared object file: No such file or > > directory - /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0/cproton.so > > (LoadError) > > > > How can I go around solving this? > > > > Disable the Ruby part of the project, unless you actually want to work on > Qpid Proton Ruby binding ;P Add option -DBUILD_BINDINGS=cpp,python to your > `cmake ..` command. That is, do not specify ruby binding. > > If you want to dig into this issue deeper, then try looking at what does > `cmake ...` print regarding sasl, or cyrus sasl? Do you have cyrus sasl > installed? > I am also suspicious of the option -DSYSINSTALL_BINDINGS. Try leaving it > out. CI does not use it either. In fact, for Proton development, you should > not need to install Proton at all, you can work from the build directory. > > On Thu, Apr 1, 2021 at 1:20 PM mehaboob shariff <mehaboob...@gmail.com> > wrote: > > > Hello Jiri, > > Thanks for the information. I don't particularly remember the tests that > > failed that were caused due to absence of Jsoncpp. > > > I tried running tests without jsoncpp installed (on Fedora Linux) and I did > not see the error you described, so I am not in the best position to > investigate. > > > > Sorry for the > > inconvenience > > > No inconvenience on my side, Proton works for me ;P > -- > Mit freundlichen Grüßen / Kind regards > Jiri Daněk >
