From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 27C15CD98E4 for ; Wed, 17 Jun 2026 10:14:15 +0000 (UTC) Subject: Re: [scarthgap][PATCH] openssl: upgrade 3.5.6 -> 3.5.7 To: openembedded-core@lists.openembedded.org From: "Sai Sneha" X-Originating-Location: IN (203.197.190.100) X-Originating-Platform: Windows Edge 149 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Wed, 17 Jun 2026 03:14:05 -0700 References: <20260616165623.3049563-1-peter.marko@siemens.com> In-Reply-To: <20260616165623.3049563-1-peter.marko@siemens.com> Message-ID: <197246.1781691245370176580@lists.openembedded.org> Content-Type: multipart/alternative; boundary="4MJQGXRaaq50pcaDm3xv" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 17 Jun 2026 10:14:15 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/239029 --4MJQGXRaaq50pcaDm3xv Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, I applied your scarthgap patch (#238923) directly via git am on a clean ori= gin/scarthgap checkout and ran the openssl ptests on QEMU (qemux86-64, defa= ult 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:6= 5792kB 41 tests pass before this ( 02-test_list.t is the last to pass), then 02-te= st_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 does= n't complete fully (TOTAL: 1 FAIL: 2). I also tested this independently on oe-core master-next (your original comm= it 9365ac47f994a7d6be92b8c011c51ecf48e8ef87 ) and on my own scarthgap backp= ort 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 t= hese tests? Thanks, Sai Sneha --4MJQGXRaaq50pcaDm3xv Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi Pet= er,

I appl= ied your scarthgap patch (#238923) directly via git am on a clean origin/sc= arthgap checkout and ran the openssl ptests on QEMU (qemux86-64, default me= mory, no manual config changes).

lhash_= test fails with an OOM kill:

=  
&nb= sp;
Out of memory=
: Killed process 546 (lhash_test) total-vm:72960kB, anon-rss:65792kB=

41 tes= ts 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-runne= r process itself also gets killed by the OOM killer, so the suite doesn't c= omplete fully (TOTAL: 1 FAIL: 2). 

I also= tested this independently on oe-core master-next (your original commit 9365ac47f= 994a7d6be92b8c011c51ecf48e8ef87) and on my own scarthgap backport sa= me 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 memor= y-availability issue rather than a problem with the patch itself.

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

Thanks= ,
Sai Sneha

--4MJQGXRaaq50pcaDm3xv--