How would that impact running multiple different instances of autopkgtest locally given keeping the data after a run? Not having the name of the package for which a run seems to make things more confusing: you'd need to track which temporary directory was used for which run, or go dig in the debian/control file.
Seems like the right location here for gains really is to shorten the test harness' directory; from say 'autopkgtest-virt-lxc' to just 'lxc'? The same logic appears to seemlessly apply to other harnesses; like qemu. We have the potential to gain as much as 17 characters here, without sacrificing in clarity of what things where used for in /tmp. Also, have you discussed this with upstream / directly with pitti? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680577 Title: Autopkgtest fails on s390x due to long PATH in test config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1680577/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
