Comment 6 for bug 1708051

@laney

After many local runs, I never see a failure of boot-smoke. I do see flakey failures of nspawn tests which is now logged in upstream tracker and will be investigated further - https://github.com/systemd/systemd/issues/6614

Reboot test failures, do mention unexpected EOF which on the surface looks related to ssh fixes in autopkgtest 4.4 and the patches to resolve a similar EOF with qemu runner reported in Debian BTS.
Next steps for me are:
* continue testing tests locally with FORCE_REBOOT_TEST=1 environment variable to continue to validate each upload (no regressions)
* pull latest autopkgtest with pending patches from git and run that with ssh runner against canonistack
* hopefully reproduce & fix the hang with canonistack assistance

I do not have any confirmation that systemd in proposed is bad.