On February 8, 2016 3:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker@xxxxxxxxxxxxx> > Cc: OpenSSH Devel List <openssh-unix-dev@xxxxxxxxxxx> > Subject: Re: [Bug] Regression problem in transfer.sh for OpenSSH 7.1 P2 on > HPE NSE above dd-size 32k > > On Tue, Feb 9, 2016 at 6:36 AM, Randall S. Becker > <rsbecker@xxxxxxxxxxxxx> wrote: > [...] > > Getting detailed debug logs of the regression test would also really > > help here. Anyone have any pointers on where I can look to try to resolve > this? > > The logs should be in the regress directory. There should be ssh.log and > ssh.log for the currently running test and failed-ssh.log and failed-sshd.log > containing the concatenation of the logs from any failed tests. You can run > "make t-exec LTESTS=transfer" to run just that single test while you're playing > around to save some time. > > I have seen something similar on old FreeBSD systems when the test was run > on an NFS mount. I never figured out why this was, but running the test on > local disk worked in that case. I've got those logs. Unfortunately, hoping for more details. The logs do show the test failure, but no details in failed-sshd.log indicating a specific problem. Some of the formats are a bit wonky but I can live with those. Since you mentioned NFS, which could have been constrained by UDP packet sizes, and this platform sometimes cannot read beyond 56Kb off disk (in some situations), it may be the read of regress/data that is failing. Any pointers where that is hiding so that I can verify that data is actually getting into sshd from the disk? Cheers, Randall _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
