Rework logging for the regression tests. Previously we would log to
authordtucker <dtucker@openbsd.org>
Wed, 1 Mar 2023 09:29:32 +0000 (09:29 +0000)
committerdtucker <dtucker@openbsd.org>
Wed, 1 Mar 2023 09:29:32 +0000 (09:29 +0000)
commitf82bd1c6327a0ab418a95aa15be2508ca2740a32
treecfa7ad7f3e60b23c41afd1e51d7e1a7476128931
parent12bf74e7d548cda721d097509ff0119821cf21bb
Rework logging for the regression tests.  Previously we would log to
ssh.log and sshd.log, but that is insufficient for tests that have more
than one concurent ssh/sshd.

Instead, we'll log to separate datestamped files in a $OBJ/log/ and
leave a symlink at the previous location pointing at the most recent
instance with an entry in regress.log showing which files were created
at each point.  This should be sufficient to reconstruct what happened
even for tests that use multiple instances of each program.  If the test
fails, tar up all of the logs for later analysis.

This will let us also capture the output from some of the other tools
which was previously sent to /dev/null although most of those will be
in future commits.
regress/usr.bin/ssh/Makefile
regress/usr.bin/ssh/agent-restrict.sh
regress/usr.bin/ssh/agent.sh
regress/usr.bin/ssh/integrity.sh
regress/usr.bin/ssh/multiplex.sh
regress/usr.bin/ssh/sshd-log-wrapper.sh [deleted file]
regress/usr.bin/ssh/test-exec.sh
regress/usr.bin/ssh/timestamp.c [new file with mode: 0644]