On Thu, 23 Jan 2014, Darren Tucker wrote: > On Thu, Jan 23, 2014 at 10:27 AM, Hisashi T Fujinaka <htodd at twofifty.com> wrote: >>> On Thu, Jan 23, 2014 at 10:12 AM, Hisashi T Fujinaka <htodd at twofifty.com> >>> wrote: >>>> >>>> On NetBSD amd64-current with a git pull on 1/22 at about 2300GMT: >>> >>> [...] >>> >>> The test framework should have created the files failed-sshd.log and >>> failed-ssh.log and failed-regress.log containing the output of the >>> failing test. >>> >>> The problem is most likely in failed-sshd.log. If it's not obvious, >>> please post all three. >> >> diff3 (if I did it right) shows the same in all three files: >> trace: generate keys >> FATAL: sshd_proxy broken > > That's not what I was expecting to see. That's the entire content of > those files? How big are they? Also take a look at ssh.log and > sshd.log. > > If that doesn't prove helpful the next step is to add "set -x" to the > top of regress/test-exec.sh and rerun the tests. It'll be somewhat > noisy but might give a clue about what's going on. ssh.log and sshd.log are even smaller and only contain: trace: generate keys FATAL: sshd_proxy broken FAIL: sshd_proxy broken I did re-run the tests after doing a build, so that might be part of it. -- Hisashi T Fujinaka - htodd at twofifty.com BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte
