On Sun, Jul 21, 2019 at 04:24:08AM -0000, Rafael David Tinoco wrote: > Somehow the lxd containers being used for autopkgtest are, likely, > different. x64 seems to be running privileged containers for need_root > tests, while armhf is not (orelse x64 selfpkgtests wouldn't pass either, > like demonstrated in previous comment).
armhf is the only architecture that runs tests in containers. All other architectures run them in VMs. (The only reason armhf doesn't use VMs is because we can't deploy an armhf VM in openstack.) > I'll suggest a hints-ubuntu test marking this as bad-test, but it seems > that the environment is bad, and not the test. Hard disagree. If the test can detect that it's running in an unprivileged container, it should skip any tests which require privileges. If the tests as a whole can't be run in an unprivileged container, then they should declare Restrictions: isolation-machine instead of Restrictions: isolation-container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828228 Title: corosync fails to start in container (armhf) bump some limits To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1828228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
