On 2/24/25 08:27, Changqing Li via lists.openembedded.org wrote:
On 2/21/25 22:34, Mathieu Dubois-Briand wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Thu Feb 20, 2025 at 4:57 AM CET, Changqing Li via lists.openembedded.org
wrote:
From: Changqing Li<changqing...@windriver.com>
In oe-core, function ldconfig_postinst_fragment use exist of
/sbin/ldconfig to decide if ldconfig is runned to generate the cache,
and function _run_ldconfig will run ldconfig to generate cache during
generate rootfs. ldconfig.service is actually not used since we have
generate ld.so.cache during do_rootfs, refer[1][2][3]. ldconfig
dependency is necessary when ldconfig not in DISTRO_FEATURES.
The reverted commit causes regression when ldconfig not in
DISTRO_FEATURES, before, without ldconfig in DISTRO_FEATURES,
ctypes.util.find_library(name) can find the lib if it is installed, now,
since ldconfig is not installed, ctypes.util.find_library(name) cannot
find the lib even if it is installed.
Here is one usecase(gtk+3 lib is installed, ctypes.util.find_library
used to find the lib):
import wx.lib.wxcairo as wxcairo
File "/usr/lib/python3.13/site-packages/wx/lib/wxcairo/{}init{}.py", line 59, in
<module>
from .wx_cairocffi import _ContextFromDC, _FontFaceFromFont
File "/usr/lib/python3.13/site-packages/wx/lib/wxcairo/wx_cairocffi.py", line 189, in
<module>
gdkLib = _findGDKLib()
File "/usr/lib/python3.13/site-packages/wx/lib/wxcairo/wx_cairocffi.py", line
181, in _findGDKLib
return _findHelper([libname], 'gdk',
"Unable to find the GDK shared library")
File "/usr/lib/python3.13/site-packages/wx/lib/wxcairo/wx_cairocffi.py", line
170, in _findHelper
raise RuntimeError(msg)
RuntimeError: Unable to find the GDK shared library
[1]https://git.openembedded.org/openembedded-core/tree/meta/classes-global/package.bbclass#n394
[2]https://git.openembedded.org/openembedded-core/tree/meta/lib/oe/rootfs.py#n316
[3]https://github.com/systemd/systemd-stable/blob/v255-stable/units/ldconfig.service
Signed-off-by: Changqing Li<changqing...@windriver.com>
---
Hi,
Thanks for your patch. However, I believe this is introducing some
regression: I've got some ptest failures on the autobuilder:
AssertionError:
Failed ptests:
{'python3': ['test_timerfd_TFD_TIMER_ABSTIME', 'python3']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/992
You can get some more advanced about ptest failures in there:
https://valkyrie.yocto.io/pub/non-release/20250221-33/testresults/qemux86-64-ptest/core-image-ptest-python3/
Can you have a look at this issue please?
Sure. I will check this.
Regards
Changqing
Hi, Mathieu
I cannot reproduce this ptest failure on my host. No failure of
test_timerfd_TFD_TIMER_ABSTIME in log.do_testimage. and the result is:
RESULTS - parselogs.ParseLogsTest.test_get_context: PASSED (0.00s)
RESULTS - parselogs.ParseLogsTest.test_parselogs: PASSED (2.71s) RESULTS
- ping.PingTest.test_ping: PASSED (0.02s) RESULTS -
ssh.SSHTest.test_ssh: PASSED (0.56s) RESULTS -
ptest.PtestRunnerTest.test_ptestrunner_expectsuccess: SKIPPED (0.00s)
RESULTS - ptest.PtestRunnerTest.test_ptestrunner_expectfail:
EXPECTEDFAIL (4455.53s) SUMMARY: core-image-ptest-python3 () - Ran 6
tests in 4458.839s core-image-ptest-python3 - OK - All required tests
passed (successes=4, skipped=1, failures=0, errors=0) DEBUG: Python
function do_testimage finished
And I checked
https://valkyrie.yocto.io/pub/non-release/20250221-33/testresults/qemux86-64-ptest/core-image-ptest-python3/,
there is no AssertionError in log.do_testimage.2624139.20250221054435
<https://valkyrie.yocto.io/pub/non-release/20250221-33/testresults/qemux86-64-ptest/core-image-ptest-python3/log.do_testimage.2624139.20250221054435>.
So I checked test_timerfd_TFD_TIMER_ABSTIME, refer [1]. Seems like this
is not related to my changes.
My commit changes RDEPENDS for package pthon3-ctype, and this is
actually no influence for poky, since poky enable distro_feature
ldconfig by default.
There are some similar timerfd issue in upstream python, I guess maybe
this is an intermittent failure of python13
[1] https://github.com/python/cpython/blob/main/Lib/test/test_os.py#L4402
[2] https://github.com/python/cpython/issues/126112
Regards
Changqing
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#211841):
https://lists.openembedded.org/g/openembedded-core/message/211841
Mute This Topic: https://lists.openembedded.org/mt/111283758/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-