On Mar 7 02:14, Damien Miller wrote:> On Wed, 6 Mar 2024, Corinna Vinschen wrote: > > > Hi Damien, > > > > On Mar 5 11:24, Damien Miller wrote: > > > > > > Hi, > > > > > > OpenSSH 9.7p1 is almost ready for release, so we would appreciate testing > > > on as many platforms and systems as possible. This is a bugfix release. > > > > Tested on Cygwin 3.5.1. > > > > I have a testsuite failure in the dynamic-forward testcase. > > > > trace: will use ProxyCommand /home/corinna/tmp/openssh/openssh-9.7p1-1.x86_64/build/regress/netcat -x 127.0.0.1:4243 -X > > trace: wait for sshd > > trace: test -D forwarding > > trace: start dynamic -D forwarding, fork to background > > trace: testing ssh socks version 4 host 127.0.0.1 (-D) > > FAIL: ssh failed with exit status 255 > > [...] > > > > I attached the tar file with the logs. > > Unfortunately the logs don't show anything of use here. This test seems > to be working in our CI > > https://github.com/openssh/openssh-portable/actions/runs/8166331476/job/22324927234#step:11:803This is weird, in particular because you're running this on the same Cygwin release. Could this be triggered by firewall settings or something like that?> I'll see if I can reproduce the failure.Thanks, Corinna
On Wed, 6 Mar 2024, Corinna Vinschen wrote:> > Unfortunately the logs don't show anything of use here. This test seems > > to be working in our CI > > > > https://github.com/openssh/openssh-portable/actions/runs/8166331476/job/22324927234#step:11:803 > > This is weird, in particular because you're running this on the same > Cygwin release. > > Could this be triggered by firewall settings or something like that?Almost certainly yes
On Wed, 6 Mar 2024, Corinna Vinschen wrote:> > Unfortunately the logs don't show anything of use here. This test seems > > to be working in our CI > > > > https://github.com/openssh/openssh-portable/actions/runs/8166331476/job/22324927234#step:11:803 > > This is weird, in particular because you're running this on the same > Cygwin release. > > Could this be triggered by firewall settings or something like that? > > > I'll see if I can reproduce the failure.I can't replicate this on CYGWIN_NT-10.0-19045 win10pro 3.5.0-1.x86_64 2024-02-01 11:02 UTC x86_64 Cygwin which is the VM I have at hand (thanks dtucker@). -d
On Thu, 7 Mar 2024 at 03:58, Corinna Vinschen <vinschen at redhat.com> wrote: [...]> > > trace: will use ProxyCommand /home/corinna/tmp/openssh/openssh-9.7p1-1.x86_64/build/regress/netcat -x 127.0.0.1:4243 -X[...]> This is weird, in particular because you're running this on the same > Cygwin release. > > Could this be triggered by firewall settings or something like that?I'd suggest checking for other processes listening in that port range (ie "netstat -an", particularly port 4243 as shown in the error, but the tests can use other ports in that range). I've had a similar problem long ago when some antivirus product was using a port in the range the tests wanted to use. -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.