From: Gyorgy Sarvari <skandigraun@gmail.com>
To: peter.marko@siemens.com,
"gudni.m.g@gmail.com" <gudni.m.g@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] sqlite3: upgrade 3.48.0 -> 3.50.2
Date: Sun, 31 Aug 2025 22:24:34 +0200 [thread overview]
Message-ID: <ca5e2dd9-fac3-489c-ae3e-8a4e7a74e708@gmail.com> (raw)
In-Reply-To: <1860EED7D31477F1.5475@lists.openembedded.org>
On 8/31/25 20:54, Gyorgy Sarvari via lists.openembedded.org wrote:
> On 7/12/25 16:25, Peter Marko via lists.openembedded.org wrote:
>> I don’t think it’s worth to send the same patch again.
>>
>> It did not fail on normal autobuilder builds which build images and
>> testimages.
>>
>> Also my private builds were fine before I sent my patches.
>>
>>
>>
>> The problem is in oe-selftest run on autobuilder, where the conditions
>> are different.
>>
>> Oe-selftest is a huge beast (taking more than a day on regular
>> machines) and AB config is hard to decode.
>>
>> I’ll eventually build it myself as part of ppc-32 support, but I’m not
>> so far yet.
>>
> I managed reproduce this on my machine.
>
> 1. Apply this patch, and do at least 50% of world build (the more the
> better, I think).
> 2. Set BB_NUMBER_THREADS = "100" in local.conf
> 3. Delete the tmp folder (but keep the sstate cache, the idea is to
> abuse it)
> 4. Start "bitbake world" again, and let it run until it runs out of
> setscene tasks, or fails.
> 5. If it doesn't fail, stop the build and go back to step 3.
>
> I don't know how frequently this reproduces, but, it looks at least 3
> out of 4 tries fail on my end.
> I will try to look at it as time allows, but if you have experience with
> sqlite, don't hold yourself back, feel free to look into this. I start
> blind here.
>
> (Btw that 100 threads for setscene isn't a killer, I'm using an aging
> Ryzen 5600G.)
A few additions:
- It reproduces 100% of the time currently on my machine
- The thread number modification isn't actually required
- It seems to fail always at the same place - if I restart bitbake world
after a failure without deleting the tmp folder, it fails again. At this
time I struggle capturing the exact task.
- The error message from pseudo is "error while loading shared
libraries: libsqlite3.so.3.50.2: cannot open shared object file: No such
file or directory"
- At the time when this error occurs, there is indeed no such file in
sysroots-components folder
- If I run "bitbake sqlite3-native" after such a failure, and do bitbake
world again, it succeeds.
- I wonder if the reason for the behavior change is the "--soname=${PV}"
argument in the new recipe. ldd shows that pseudo is linked against
"libsqlite3.so.3.50.2", but before this patch it linked against
"libsqlite3.so.0". I suspect that until now it fell back to the host
OS's libsqlite, and that's why it didn't fail. (My main OS has 3.50.4,
so it doesn't match)
But I will stop spamming for the day, will try that tomorrow, unless
someone else is faster.
>>
>>
>> Peter
>>
>>
>>
>> *From:*openembedded-core@lists.openembedded.org
>> <openembedded-core@lists.openembedded.org> *On Behalf Of *Guðni Már
>> Gilbert via lists.openembedded.org
>> *Sent:* Saturday, July 12, 2025 16:12
>> *To:* openembedded-core@lists.openembedded.org
>> *Subject:* Re: [OE-core] [PATCH] sqlite3: upgrade 3.48.0 -> 3.50.2
>>
>>
>>
>> Previous discussion thread:
>> https://lists.openembedded.org/g/openembedded-core/topic/113866512
>>
>>
>>
>> I built today /core-image-minimal/ on latest master (Git HEAD for
>> reference:
>> https://git.openembedded.org/openembedded-core/commit/?id=cf89a121f93e404485983b92abc88a46a7f24890)
>> and also upgraded SQLite from 3.50.1 to 3.50.2 for bug fixes.
>>
>>
>>
>> So far I haven't been able to reproduce the issue with pseudo I saw
>> with SQLite 3.50.1, and I wonder if the autobuilder/test system will
>> catch any issues?
>>
>>
>>
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#222635): https://lists.openembedded.org/g/openembedded-core/message/222635
> Mute This Topic: https://lists.openembedded.org/mt/114116736/6084445
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2025-08-31 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 14:06 [PATCH] sqlite3: upgrade 3.48.0 -> 3.50.2 Guðni Már Gilbert
2025-07-12 14:12 ` Guðni Már Gilbert
2025-07-12 14:25 ` [OE-core] " Marko, Peter
2025-08-31 18:54 ` Gyorgy Sarvari
[not found] ` <1860EED7D31477F1.5475@lists.openembedded.org>
2025-08-31 20:24 ` Gyorgy Sarvari [this message]
[not found] ` <1860F3C42441CCDB.24627@lists.openembedded.org>
2025-09-01 10:29 ` Gyorgy Sarvari
2025-09-01 11:15 ` Alexander Kanavin
[not found] ` <186124667AD72DDE.24627@lists.openembedded.org>
2025-09-01 12:06 ` Alexander Kanavin
2025-09-03 22:31 ` Marko, Peter
2025-09-04 10:23 ` Alexander Kanavin
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=ca5e2dd9-fac3-489c-ae3e-8a4e7a74e708@gmail.com \
--to=skandigraun@gmail.com \
--cc=gudni.m.g@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.