I triaged this as a wishlist item, looks like we agree it is. This would be nice to have but is not trivial to implement as all the virt server would need to be covered, each with its own way of getting a shell on the testbed system.
-- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2012514 Title: $HOME is not set in --shell-fail prompt Status in autopkgtest package in Ubuntu: Triaged Bug description: Steps to reproduce: pull-lp-source hello cd hello-* # Stick "exit 1" into debian/tests/upstream-tests so it will fail dpkg-buildpackage -us -uc -S -sd -nc -d cd .. autopkgtest -s -B *dsc -- lxd ubuntu-daily:lunar echo $HOME # Actual behaviour: $HOME is unset; expected behaviour: $HOME is set $ dpkg-query -W autopkgtest autopkgtest 5.25ubuntu4 I tried this on sid with the null runner, and $HOME was set correctly there. This might be a consequence of the null runner not resetting the environment (as might be expected), or point to a bug specifically in the lxd runner; I'm not sure. I did find that $HOME is set in the actual test run. But then my test- in-development started failing in other ways because $HOME was not set in the --shell-fail environment. What I expect is that the --shell- fail environment is identical; otherwise it's difficult for debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2012514/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
