Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Sai Sneha" <saisneha196@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH] openssl: upgrade 3.5.6 -> 3.5.7
Date: Wed, 17 Jun 2026 03:14:05 -0700	[thread overview]
Message-ID: <197246.1781691245370176580@lists.openembedded.org> (raw)
In-Reply-To: <20260616165623.3049563-1-peter.marko@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hi Peter,

I applied your scarthgap patch (#238923) directly via git am on a clean origin/scarthgap checkout and ran the openssl ptests on QEMU (qemux86-64, default memory, no manual config changes).

lhash_test fails with an OOM kill:

Out of memory: Killed process 546 (lhash_test) total-vm:72960kB, anon-rss:65792kB

41 tests pass before this ( 02-test_list.t is the last to pass), then 02-test_lhash.t fails with exit code 137 (SIGKILL). Later in the run, the ptest-runner process itself also gets killed by the OOM killer, so the suite doesn't complete fully (TOTAL: 1 FAIL: 2).

I also tested this independently on oe-core master-next (your original commit 9365ac47f994a7d6be92b8c011c51ecf48e8ef87 ) and on my own scarthgap backport same lhash_test OOM occurs in all three cases under default QEMU memory. When I manually bumped QEMU's memory to 1GB, lhash_test passes, so it's a memory-availability issue rather than a problem with the patch itself.

Is this a known/expected limitation with the default qemux86-64 ptest QEMU memory, or is there something I should configure differently when running these tests?

Thanks,
Sai Sneha

[-- Attachment #2: Type: text/html, Size: 3303 bytes --]

  reply	other threads:[~2026-06-17 10:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 16:56 [scarthgap][PATCH] openssl: upgrade 3.5.6 -> 3.5.7 Peter Marko
2026-06-17 10:14 ` Sai Sneha [this message]
2026-06-17 10:30   ` [OE-core] " Marko, Peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=197246.1781691245370176580@lists.openembedded.org \
    --to=saisneha196@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox