Am I right in thinking that the limits being too low are causing false
positives in autopkgtests?
If so, we could check the limits in the test themselves and skip (exit
77 and declare "skippable") if on armhf and the limits aren't high
enough. That's a reasonable action for the packages, I think.
** Changed in: corosync (Ubuntu)
Status: New => Triaged
** Changed in: pacemaker (Ubuntu)
Status: New => Triaged
** Changed in: corosync (Ubuntu)
Importance: Undecided => Medium
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => Medium
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
