From: Changqing Li <changqing.li@windriver.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] perl: upgrade from 5.40.2 to 5.42.0
Date: Thu, 26 Feb 2026 19:23:04 +0800 [thread overview]
Message-ID: <94d7efaf-3e81-4cbf-b2e2-9e419ece0010@windriver.com> (raw)
In-Reply-To: <DGNYN4ICGR5R.29DIPU8EA51MG@bootlin.com>
On 2/25/26 18:11, 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 Tue Feb 24, 2026 at 2:46 AM CET, Changqing Li via lists.openembedded.org wrote:
>> License-Update: Update copies of GPL to match recent FSF changes
>>
>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
>> ---
> Hi Changqing,
>
> Thanks for your patch.
>
> It looks like some ptest is failing. I suspect the fail comes from the
> perl upgrade:
>
> WARNING: core-image-ptest-libmodule-build-perl-1.0-r0 do_testimage: There were failing ptests.
> Traceback (most recent call last):
> File "/srv/pokybuild/yocto-worker/qemux86-64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
> return func(*args, **kwargs)
> File "/srv/pokybuild/yocto-worker/qemux86-64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
> return func(*args, **kwargs)
> File "/srv/pokybuild/yocto-worker/qemux86-64-ptest/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
> return func(*args, **kwargs)
> File "/srv/pokybuild/yocto-worker/qemux86-64-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 27, in test_ptestrunner_expectfail
> self.do_ptestrunner()
> File "/srv/pokybuild/yocto-worker/qemux86-64-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 120, in do_ptestrunner
> self.fail(failmsg)
> AssertionError:
> Failed ptests:
> {'libmodule-build-perl': ['t/xs']}
Hi, Mathieu,
I cannot reproduce this locally, in my test env, the missing package
is installed as a dependency by someone.
But I think I have find the issue and send V2, please help to test with
V2. Thanks.
Regards
Changqing
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3155
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3114
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1126
>
> Test logs can be found here:
>
> https://valkyrie.yocto.io/pub/non-release/20260225-48/testresults/qemuarm64-ptest/core-image-ptest-libmodule-build-perl/
> https://valkyrie.yocto.io/pub/non-release/20260225-48/testresults/qemux86-64-ptest/core-image-ptest-libmodule-build-perl/
>
> Can you have a look at the issues?
>
> Thanks,
> Mathieu
>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
next prev parent reply other threads:[~2026-02-26 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:46 [PATCH] perl: upgrade from 5.40.2 to 5.42.0 Changqing Li
2026-02-25 10:11 ` [OE-core] " Mathieu Dubois-Briand
2026-02-26 11:23 ` Changqing Li [this message]
2026-02-26 11:24 ` [PATCH V2] " 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=94d7efaf-3e81-4cbf-b2e2-9e419ece0010@windriver.com \
--to=changqing.li@windriver.com \
--cc=mathieu.dubois-briand@bootlin.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