Add report progress infrastructure #173
Annotations
3 errors and 2 warnings
Microsoft.DevTunnels.Ssh.Test.InteropTests ► InteropJumpHostTest:
test/cs/Ssh.Test/InteropTests.cs#L647
Failed test found in:
out/TestResults/SSH-CS-net6.0.trx
Error:
System.Exception : Did not execute test command "echo abc"
sshd process output follows:
/usr/sbin/sshd -D -e -o "LogLevel=VERBOSE" -p 50851 -f "/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpuxgBgY.tmp" -o "AuthorizedKeysFile=/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmp05iFu7.tmp" -o "StrictModes=no" -o "PidFile=/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpBGLwt3.tmp" -o "HostKey=/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpwkcVjE.tmp"
Server listening on :: port 50851.
Server listening on 0.0.0.0 port 50851.
Connection from 127.0.0.1 port 50854 on 127.0.0.1 port 50851
Accepted key RSA SHA256:UdKZmXZ2rURV154YmcuBalwjCUyCRUc/CoBSeJ43Gf4 found at /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmp05iFu7.tmp:1
Accepted publickey for runner from 127.0.0.1 port 50854 ssh2: RSA SHA256:UdKZmXZ2rURV154YmcuBalwjCUyCRUc/CoBSeJ43Gf4
BSM audit: bsm_audit_session_setup: setaudit_addr failed: Operation not permitted
User child is on pid 4434
Starting session: command for runner from 127.0.0.1 port 50854 id 0
ssh process output follows:
/usr/bin/ssh -v -F "/var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp" TargetSsh "echo abc"
OpenSSH_8.6p1, LibreSSL 3.3.6
debug1: Reading configuration data /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp
debug1: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp line 8: Applying options for TargetSsh
debug1: Setting implicit ProxyCommand from ProxyJump: /usr/bin/ssh -F /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp -v -W '[%h]:%p' VSSsh
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Executing proxy command: exec /usr/bin/ssh -F /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp -v -W '[127.0.0.1]:50851' VSSsh
debug1: identity file /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp type -1
debug1: identity file /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.6
OpenSSH_8.6p1, LibreSSL 3.3.6
debug1: Reading configuration data /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp
debug1: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpE8J0n4.tmp line 1: Applying options for VSSsh
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 50852.
debug1: Connection established.
debug1: identity file /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp type -1
debug1: identity file /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.6
debug1: Remote protocol version 2.0, remote software version Microsoft.DevTunnels.Ssh_3.11
debug1: compat_banner: no match: Microsoft.DevTunnels.Ssh_3.11
debug1: Authenticating to 127.0.0.1:50852 as 'testuser'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group14-sha256
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: aes256-ctr MAC: hmac-sha2-512 compression: none
debug1: kex: client->server cipher: aes256-ctr MAC: hmac-sha2-512 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-rsa SHA256:UHnN+H+f4XQFXHE7FMWLISczBNdqwAfJIuXz5eNu3pY
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '[127.0.0.1]:50852' is known and matches the RSA host key.
debug1: Found key in /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpYec2Dc.tmp:2
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: Will attempt key: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: open-channel-request@microsoft.com (unrecognised)
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: none,password,publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp
debug1: Authentication succeeded (publickey).
Authenticated to 127.0.0.1 ([127.0.0.1]:50852).
debug1: channel_connect_stdio_fwd: 127.0.0.1:50851
debug1: channel 0: new [stdio-forward]
debug1: getpeername failed: Bad file descriptor
debug1: Entering interactive session.
debug1: pledge: network
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.6
debug1: compat_banner: match: OpenSSH_8.6 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 127.0.0.1:50851 as 'runner'
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-rsa SHA256:UHnN+H+f4XQFXHE7FMWLISczBNdqwAfJIuXz5eNu3pY
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '[127.0.0.1]:50851' is known and matches the RSA host key.
debug1: Found key in /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpYec2Dc.tmp:1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmpp6WFuL.tmp
debug1: Authentication succeeded (publickey).
Authenticated to 127.0.0.1 (via proxy).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: proc
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Remote: /var/folders/3s/vfzpb5r51gs6y328rmlgzm7c0000gn/T/tmp05iFu7.tmp:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug1: Sending command: echo abc
---- System.Exception : Did not execute test command "echo abc"
|
Build SSH on macOS-latest
Failed test were found and 'fail-on-error' option is set to true
|
Build SSH on macOS-latest
Process completed with exit code 1.
|
Build SSH on windows-latest
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|
Build SSH on macOS-latest
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|