Page MenuHomePhabricator

torture_proxycommand failing
Open, Needs TriagePublic

Description

Currently, every version of libssh I've tried (0.8.6, 0.8.7, and current master) consistently fail on torture_proxycommand if client testing is enabled:

Test project /home/ivaldi/packages/newpkg/libssh/obj-aarch64-linux-gnu

Start 42: torture_proxycommand

1/1 Test #42: torture_proxycommand .............***Failed 0.52 sec
[==========] Running 3 test(s).
OK: SSH-2.0-OpenSSH_7.9
[ RUN ] torture_options_set_proxycommand
[ ERROR ] --- ERROR: Invalid return code - Socket error: Connection reset by peer
[ LINE ] --- /home/ivaldi/packages/newpkg/libssh/tests/client/torture_proxycommand.c:77: error: Failure!
[ FAILED ] torture_options_set_proxycommand
[ RUN ] torture_options_set_proxycommand_notexist
[ OK ] torture_options_set_proxycommand_notexist
[ RUN ] torture_options_set_proxycommand_ssh
[ OK ] torture_options_set_proxycommand_ssh
[==========] 3 test(s) run.
[ PASSED ] 2 test(s).
[ FAILED ] 1 test(s), listed below:
[ FAILED ] torture_options_set_proxycommand

1 FAILED TEST(S)

Client testing is apparently not enabled by default, so of course this is probably going unnoticed in regular unit-testing.

This is with openssl 1.1.0j on aarch64 little-endian, Linux 4.16.18.

Event Timeline

kelledin created this task.Apr 9 2019, 9:19 AM

Hello,

Actually the client testing is enabled in most of the builds in the CI (you can check the CI configuration in .gitlab-ci.yml file).

Can you please rerun the test in the failing environment with a more verbose setting? You can run it like this:

$ LIBSSH_VERBOSITY=4 ctest -V -R torture_proxycommand
asn added a subscriber: asn.Jun 14 2019, 12:04 PM

Is this using musl libc?