public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Xiangyu Chen <xiangyu.chen@eng.windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] lttng-tools: skip lttng kernel related test if lttng kernel modules not present
Date: Fri, 8 Mar 2024 09:33:15 +0800	[thread overview]
Message-ID: <7468d1dc-182e-4e49-b462-dcdb7505feea@eng.windriver.com> (raw)
In-Reply-To: <15817651ba1ade33b769061f772cfab961aba996.camel@linuxfoundation.org>


On 2/10/24 00:44, Richard Purdie 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 Wed, 2024-01-31 at 11:40 +0800, Xiangyu Chen wrote:
>> From: Xiangyu Chen <xiangyu.chen@windriver.com>
>>
>> The current tests will run both userspace and kernel testing. Some of use cases only
>> use lttng for one kind of tracing (e.g. userspace). If the lttng modules(.ko files)
>> is not present during the test,it would end up with lots of failing.
>>
>> Add a check in ptest script, if current system doesn't contain lttng kernel modules,
>> passing LTTNG_TOOLS_DISABLE_KERNEL_TESTS=1 to make to skip all lttng kernel related testing.
>>
>> Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
>> ---
>>   ...skip_kernel_test-to-check-root-user-.patch | 1307 +++++++++++++++++
>>   .../lttng/lttng-tools/run-ptest               |   25 +
>>   .../lttng/lttng-tools_2.13.11.bb              |    1 +
>>   3 files changed, 1333 insertions(+)
>>   create mode 100644 meta/recipes-kernel/lttng/lttng-tools/0001-tests-add-check_skip_kernel_test-to-check-root-user-.patch
> This is a complex patch and I don't really want to carry this until
> something merges upstream or ideally makes it into a released version.

Hi Richard,


Thanks for your suggestion,

lttng upstream has merged this patch, I'll send a v2 patch to oe-core 
later after a simple testing in my local setup.


Br,

Xiangyu

>
> We simply don't have the maintainer capacity to carry large patches
> like this unfortunately and the number of people who need it isn't
> clear.
>
> Cheers,
>
> Richard


      reply	other threads:[~2024-03-08  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  3:40 [OE-core][PATCH] lttng-tools: skip lttng kernel related test if lttng kernel modules not present Xiangyu Chen
2024-02-09 16:44 ` Richard Purdie
2024-03-08  1:33   ` Xiangyu Chen [this message]

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=7468d1dc-182e-4e49-b462-dcdb7505feea@eng.windriver.com \
    --to=xiangyu.chen@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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