| Message ID | 20251224130314.1717117-1-richard.purdie@linuxfoundation.org |
|---|---|
| State | Accepted, archived |
| Commit | 2e4c9b8dee3b1d545aee354ac1f8c6a5c0bad433 |
| Headers | show |
| Series | oeqa/selftest/glibc: Increase VM memory | expand |
diff --git a/meta/lib/oeqa/selftest/cases/glibc.py b/meta/lib/oeqa/selftest/cases/glibc.py index 0838e8ac33c..b2b115972ff 100644 --- a/meta/lib/oeqa/selftest/cases/glibc.py +++ b/meta/lib/oeqa/selftest/cases/glibc.py @@ -70,7 +70,7 @@ class GlibcSelfTestBase(OESelftestTestCase, OEPTestResultTestCase): bitbake("core-image-minimal") # start runqemu - qemu = s.enter_context(runqemu("core-image-minimal", runqemuparams = "nographic", qemuparams = "-m 1024")) + qemu = s.enter_context(runqemu("core-image-minimal", runqemuparams = "nographic", qemuparams = "-m 2048")) # validate that SSH is working status, _ = qemu.run("uname")
We're seeing OOM killer issues when testing glibc on KVM system mode testing which leads to hanging selftests on the autobuilder. The processes killed in the images are semi-random. Increase the memory size to avoid these hanging builds. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- meta/lib/oeqa/selftest/cases/glibc.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)