Although things looked good on testing at first (local amd64), you can see there that arm and s390x seem to fail now.
ARM:
run test connect.sh ...
ssh-keygen -lf /tmp/autopkgtest.U8eLXQ/autopkgtest_tmp/tree/regress/t12.out.pub | grep test-comment-1234 >/dev/null
ssh connect with protocol 2 failed
make: *** [t-exec] Error 1
failed simple connect
s390x:
run test forwarding.sh ...
failed copy of /bin/ls
cmp: EOF on /data/adttmp/autopkgtest-virt-lxc.shared.j0fd9gxe/downtmp/autopkgtest_tmp/tree/regress/copy
corrupted copy of /bin/ls
failed local and remote forwarding
Thanks Colin,
I have new bileto tickets with all the fixes prepared:
Xenial: https:/ /bileto. ubuntu. com/#/ticket/ 2597 /bileto. ubuntu. com/#/ticket/ 2598
Yakkety: https:/
Although things looked good on testing at first (local amd64), you can see there that arm and s390x seem to fail now.
ARM: t.U8eLXQ/ autopkgtest_ tmp/tree/ regress/ t12.out. pub | grep test-comment-1234 >/dev/null
run test connect.sh ...
ssh-keygen -lf /tmp/autopkgtes
ssh connect with protocol 2 failed
make: *** [t-exec] Error 1
failed simple connect
s390x: autopkgtest- virt-lxc. shared. j0fd9gxe/ downtmp/ autopkgtest_ tmp/tree/ regress/ copy
run test forwarding.sh ...
failed copy of /bin/ls
cmp: EOF on /data/adttmp/
corrupted copy of /bin/ls
failed local and remote forwarding
These reproduce in 4/4 cases :-/ autopkgtest. ubuntu. com/packages/ openssh/ xenial/ armhf autopkgtest. ubuntu. com/packages/ openssh/ yakkety/ armhf autopkgtest. ubuntu. com/packages/ openssh/ xenial/ s390x autopkgtest. ubuntu. com/packages/ openssh/ yakkety/ s390x
Then I checked history and it seems those are accepted and ignored cases all through Xenial/Yakkety.
See:
http://
http://
http://
http://
Same failure since:
- Xenial openssh 1:7.2p2-4ubuntu2.1
- Yakkety systemd/231-3
That said, Colin - would you mind to sponsor by hitting "publish" on those two tickets after you synced the latest Debian to Zesty?