Review: Disapprove Because armhf runners are containers instead of VMs (and thus have no per-runner memory limits), big_packages will have no effect here. You can try rerunning and hope there is not memory contention on the lxd host at the time it is run. But I don't see anything in the log that specifically points to an OOM condition.
Bear in mind that armhf is our only 32-bit arch as well, you might be running into address space issues rather than OOM. -- https://code.launchpad.net/~lvoytek/autopkgtest-cloud/+git/autopkgtest-package-configs/+merge/446971 Your team Canonical's Ubuntu QA is subscribed to branch ~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs:main. -- 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
