Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Yu, Mingli" <mingli.yu@windriver.com>,
	"Joao Marcos Costa" <joaomarcos.costa@bootlin.com>,
	<mingli.yu@eng.windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 2/4] babeltrace2: Enable python plugins
Date: Thu, 24 Jul 2025 11:53:33 +0200	[thread overview]
Message-ID: <DBK6ZO3Y41DP.3T6QCFS3ID77W@bootlin.com> (raw)
In-Reply-To: <b955127c-37e5-401d-915e-af8e2ab51bb2@windriver.com>


[-- Attachment #1.1: Type: text/plain, Size: 2233 bytes --]

On Thu Jul 24, 2025 at 7:58 AM CEST, Mingli Yu wrote:
>
>
> On 7/23/25 13:51, 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.
>> 
>>>> There are some ptest errors in the autobuilder:
>>>> -
>>>> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1923/steps/12/logs/stdio
>>>> -
>>>> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/73/builds/1931/steps/12/logs/stdio
>>>>
>>>> Could you please take a look?
>>>
>>> I will look into this.
>>>
>>> Could I access the ptest-runner.log such as
>>> tmp/work/qemux86_64-poky-linux/core-image-ptest-babeltrace2/1.0/testimage/ptest_log.20250710153833/ptest-runner.log
>>> corresponding to
>>> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1923/steps/12/logs/stdio?
>> 
>> Hi Mingli,
>> 
>> Ptest logs can be found here:
>> 
>> https://valkyrie.yocto.io/pub/non-release/20250720-85/testresults/qemuarm64-ptest/core-image-ptest-lttng-tools/
>> https://valkyrie.yocto.io/pub/non-release/20250720-85/testresults/qemux86-64-ptest/core-image-ptest-lttng-tools/
>
> I didn't find ptest-runner.log under the location you pointed.
> The ptest-runner.log such as 
> tmp/work/qemux86_64-poky-linux/core-image-ptest-babeltrace2/1.0/testimage/ptest_log.20250710153833/ptest-runner.log.
>
> Thanks,
> Mingli
>
>> 
>>>
>>> Thanks,
>>> Mingli
>>>
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> Best regards,
>>>> João Marcos Costa
>> 
>> --
>> Mathieu Dubois-Briand, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>> 

Ok, I relaunched a build, to be able to capture this file. I've attached
tmp/work/qemuarm64-poky-linux/core-image-ptest-babeltrace2/1.0/testimage/ptest_log.20250724082617/ptest-runner.log
to this mail.

https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1951
https://valkyrie.yocto.io/pub/non-release/20250720-85/testresults/qemux86-64-ptest/core-image-ptest-babeltrace2/

Best regards,
Mathieu

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

[-- Attachment #2: ptest-runner.log.bz2 --]
[-- Type: application/x-bzip, Size: 335685 bytes --]

  reply	other threads:[~2025-07-24  9:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-20  9:00 [PATCH v2 1/4] lttng-ust: Upgrade 2.13.9 -> 2.14.0 mingli.yu
2025-07-20  9:00 ` [PATCH v2 2/4] babeltrace2: Enable python plugins mingli.yu
2025-07-21  8:09   ` [OE-core] " Joao Marcos Costa
2025-07-23  2:10     ` Yu, Mingli
2025-07-23  5:51       ` Mathieu Dubois-Briand
2025-07-24  5:58         ` Yu, Mingli
2025-07-24  9:53           ` Mathieu Dubois-Briand [this message]
2025-07-20  9:00 ` [PATCH v2 3/4] lttng-tools: Upgrade 2.13.15 -> 2.14.0 mingli.yu
2025-07-20  9:00 ` [PATCH v2 4/4] lttng-tools: Remove the scope resolution operator with musl mingli.yu
2025-07-21  9:39   ` [OE-core] " Alexander Kanavin
2025-07-23  2:13     ` Yu, Mingli
2025-07-23 10:08       ` Alexander Kanavin
2025-07-22  1:23   ` Khem Raj

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=DBK6ZO3Y41DP.3T6QCFS3ID77W@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=joaomarcos.costa@bootlin.com \
    --cc=mingli.yu@eng.windriver.com \
    --cc=mingli.yu@windriver.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