Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <mathieu.dubois-briand@bootlin.com>,
	"Changqing Li" <changqing.li@windriver.com>,
	<openembedded-core@lists.openembedded.org>,
	<joerg.sommer@navimatix.de>
Subject: Re: [OE-core] [PATCH] Revert "python3-ctypes: depend on ldconfig only if distro-feature set"
Date: Tue, 25 Feb 2025 10:12:29 +0100	[thread overview]
Message-ID: <D81ET1Y1GAYL.3AI2RCOQLK8GS@bootlin.com> (raw)
In-Reply-To: <18271FF8E1B74516.20721@lists.openembedded.org>

On Mon Feb 24, 2025 at 12:02 PM CET, Mathieu Dubois-Briand via lists.openembedded.org wrote:
> On Mon Feb 24, 2025 at 9:20 AM CET, Changqing Li wrote:
> >
> > On 2/24/25 08:27, Changqing Li via lists.openembedded.org wrote:
> > 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
>
> Hi Changqing,
>
> Thanks for testing. This might be a intermittent failure, but I believe
> we never saw this one before.
>
> I will add back this patch in my branch and let's see how it goes!

Hi Changqing,

I confirm I added this back and now it's working. So it might be some
new AB-INT issue, nothing is wrong with your patch from the autobuilder
perspective.

Thanks for your time.

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2025-02-25  9:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  3:57 [PATCH] Revert "python3-ctypes: depend on ldconfig only if distro-feature set" changqing.li
2025-02-21 14:34 ` [OE-core] " Mathieu Dubois-Briand
2025-02-24  0:27   ` Changqing Li
     [not found]   ` <1826FD59DBA1FC0B.20721@lists.openembedded.org>
2025-02-24  8:20     ` Changqing Li
2025-02-24 11:02       ` Mathieu Dubois-Briand
     [not found]       ` <18271FF8E1B74516.20721@lists.openembedded.org>
2025-02-25  9:12         ` Mathieu Dubois-Briand [this message]
2025-02-24 23:36 ` Jörg Sommer
2025-02-25  2:02   ` Changqing Li
2025-02-25  5:33     ` Jörg Sommer
2025-02-27 22:32     ` Jörg Sommer
2025-02-28  2:56       ` Changqing Li
2025-02-28  5:42         ` Jörg Sommer
2025-02-28 10:20           ` Richard Purdie
2025-02-28 10:35             ` Jörg Sommer
2025-02-28 10:50               ` Richard Purdie
2025-03-03  3:30                 ` Changqing Li

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=D81ET1Y1GAYL.3AI2RCOQLK8GS@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=changqing.li@windriver.com \
    --cc=joerg.sommer@navimatix.de \
    --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