Call for testing: OpenSSH 6.6

[Kevin Brott]

Running test-exec.sh with the set -x in it shows it trying to run this
command line:
/usr/src/openssh/regress/sshd -f /usr/src/openssh/regress/sshd_config
-E/usr/src/openssh/regress/ssh.log
Yet, watching the process table during that part of make tests shows that
command never actually executed, so the pidfile being tested for never
materializes.

Simply manually running that command  in another window while the test is
waiting for the pidfile, gets past the failure and gets 'make tests' to
cleanly finish to 'all tests passed'.

So I'm not sure exactly what's going south here, it's almost as if it's not
really running the command, or can't - but it's not throwing any errors as
to why.

=====

On Thu, Mar 6, 2014 at 3:43 PM, Tim Rice <tim at multitalents.net> wrote:

> On Thu, 6 Mar 2014, Kevin Brott wrote:
>
> > So - trying to build openssh-SNAP-20140307.tar.gz on RHEL 4 (SP8) x86_64
> > and I'm hitting a wall in 'make tests':
> >
> > ...
> > ok connection multiplexing
> > run test reexec.sh ...
> > test config passing
> > reexec tests: proto 1
> > reexec tests: proto 2
> > test reexec fallback
> > FATAL: no sshd running on port 4242
> > gmake[1]: *** [t-exec] Error 1
> > gmake[1]: Leaving directory `/var/tmp/ssh/openssh/regress'
> > gmake: *** [tests] Error 2
> >
> [snip]
> > The weirder thing is that I got this to work in the i386 test box just
> > fine. Thoughts?
>
> You can use "make LTESTS=reexec tests" to just run the single test.
> sshd gets started by test-exec.sh, so you could put a set -x in there
> to capture the actual command line used the try it manually or
> under strace to see what's going on.
>
> --
> Tim Rice                                Multitalents
> tim at multitalents.net
>
>
>


-- 
# include <stddisclaimer.h>
/* Kevin  Brott <Kevin.Brott at gmail.com> */