Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
	<openembedded-core@lists.openembedded.org>
Cc: <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH] lttng-ust: add ptest support
Date: Sat, 31 Oct 2026 09:38:30 +0100	[thread overview]
Message-ID: <DMIVYZC6OZUY.K8JSSXN15YSD@bootlin.com> (raw)
In-Reply-To: <20261029131154.7487-1-pratik.farkase@est.tech>

On Thu Oct 29, 2026 at 2:11 PM CET, Pratik Farkase wrote:
> Build and run the lttng-ust unit test suite under ptest, modelled on the
> liburcu ptest support: the run-ptest script executes each TAP test from
> the tests/unit subdirectories and reports PASS/FAIL. The compile tests,
> benchmarks and the abi0-conflict regression test (unstable under QEMU)
> are excluded.
>
> The ust-elf test ships prebuilt, intentionally foreign-architecture ELF
> fixtures, so they are kept from being stripped and the related QA checks
> are relaxed for the ptest package.
>
> Tested on qemuriscv64 with ptest-runner.
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---

Hi Pratik,

It looks like one of the tests is failing:

WARNING: core-image-ptest-lttng-ust-1.0-r0 do_testimage: There were failing ptests.
Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/qemuarm64-musl-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/qemuarm64-musl-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/qemuarm64-musl-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/qemuarm64-musl-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/qemuarm64-musl-ptest/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/ptest.py", line 121, in do_ptestrunner
    self.fail(failmsg)
AssertionError:
Failed ptests:
{'lttng-ust': ['unit/ust-error/test_ust_error']}

https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1469
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1491

Can you have a look at the issue?

Thanks,
Mathieu

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


  reply	other threads:[~2026-10-31  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 13:11 [OE-core][PATCH] lttng-ust: add ptest support Pratik Farkase
2026-10-31  8:38 ` Mathieu Dubois-Briand [this message]
2026-11-03  8:57 ` [OE-core][PATCH v2] " Pratik Farkase
2026-11-03  9:01   ` Patchtest results for " patchtest
2026-11-03  9:07 ` Pratik Farkase
2026-11-05 11:38   ` Alexander Kanavin
2026-11-16  9:52 ` [OE-core][PATCH v3] " Pratik Farkase

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=DMIVYZC6OZUY.K8JSSXN15YSD@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pratik.farkase@ericsson.com \
    --cc=pratik.farkase@est.tech \
    /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