search for: prodstack4

...Make integrity tests more robust against timeouts If the first test in a series for a given MAC happens to modify the low bytes of a packet length, then ssh will time out and this will be interpreted as a test failure. I'm seeing this in practice on Ubuntu ppc64el (e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/o/openssh/20161231_121729_ebc8a@/log.gz). Fortunately there was already an XXX comment indicating what might be going wrong here, and although I haven't been able to reproduce it directly on a system where...

...Created attachment 2926 --> https://bugzilla.mindrot.org/attachment.cgi?id=2926&action=edit Create mux socket for regress in temp directory In some setups, creating the socket under OBJ may result in a path that is too long for a Unix domain socket. The failure in https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/s390x/o/openssh/20170103_003152_0b07a@/log.gz was due to this. While of course it's possible to say that everyone must ensure that OBJ is short enough to avoid exceeding this limit, the limit is quite low at least...

...: mm_request_receive entering debug1: do_cleanup debug1: audit_event: unhandled event 12 FAIL: failed copy of /bin/ls FAIL: corrupted copy of /bin/ls Full output here: https://ci.debian.net/data/packages/unstable/amd64/o/openssh/20161231_044927.autopkgtest.log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/s390x/o/openssh/20161231_120523_ebc8a@/log.gz Thanks, -- Colin Watson [cjwatson at debian.org]