python-ruffus kills LXC worker on ppc64el
Bug #1488879 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Fix Released
|
High
|
Martin Pitt | ||
autopkgtest (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
python-ruffus' tests create some kind of python fork bomb in ppc64el's LXC worker, which triggers the OOM killer.
We need to find a way for the spawned LXC container to be the first OOM victim, instead of killing the worker python process.
Related branches
Changed in auto-package-testing: | |
importance: | Undecided → High |
status: | New → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
Changed in autopkgtest (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Martin Pitt (pitti) |
no longer affects: | autopkgtest (Ubuntu) |
Changed in autopkgtest (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Martin Pitt (pitti) |
To post a comment you must log in.
Setting "lxc.cgroup. memory. limit_in_ bytes = 1800M" in /usr/share/ lxc/config/ ubuntu. common. conf does the trick for not killing host processes. I. e. leave enough room for two parallel testbeds plus some for the host OS.
After that, adt-run still fails to properly kill the container and clean up.