New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: pick a random port number for SSH #5273
Conversation
67a6ab7
to
e925814
Compare
Since sshd doesn't have such an option by itself, we iterate over a series of random ports until one works. Closes #5273
e925814
to
ec1442d
Compare
When trying out this method, I spotted that it doesn't work on Cirrus-CI. I then went back and noticed that the SSH server was never started/used fine on Cirrus so this isn't new with this PR. The reason seems to be that the "verification" of the server with the sftp command fails. This is the hint in the sftp server log:
According to sources "on the internet" this (the "message too long") is typically the result of the user having |
Please give me a chance to test this locally on Windows before merging. I will try to do that now. |
I haven't got the SSH tests working on Windows again yet, regardless of this PR. I will retry tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is passing my local tests on Windows
Since sshd doesn't have such an option by itself, we iterate over a
series of random ports until one works.