Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Etienne Cordonnier <ecordonnier@snap.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/runtime: fix regression in minidebuginfo test
Date: Tue, 04 Jun 2024 13:32:25 +0100	[thread overview]
Message-ID: <d3de56017f5df0786dc58d50308d9c76dfdd85cb.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAHUKmYbGNATvoBq2pUFbvOF_HK922onqQctMn444_9Jaz1XxaA@mail.gmail.com>

On Tue, 2024-06-04 at 13:58 +0200, Etienne Cordonnier wrote:
> I'm talking specifically about test_systemd_coredump_minidebuginfo
> (the minidebuginfo test which I wrote
> in meta/lib/oeqa/runtime/cases/systemd.py, not the tests
> in meta/lib/oeqa/selftest/cases/minidebuginfo.py).

Ok, sorry, I'm struggling to remember all the right context!

I get nervous about blanket distro changes as whilst it adds test
coverage to minidebuginfo, it also removes test coverage from other
things (the non-mini systemd case).

How are we all runtime coverage to the selftest in question, so it
boots and runs the systemd selftests?

Specifically, we'd add config along the lines of:


DISTRO_FEATURES:append = " systemd"
TEST_SUITES = "ping ssh systemd"

and then add a:

bitbake('-c testimage core-image-minimal')

to that testcase in selftest, which would then ensure we do run the
right tests?

If we want to test both the systemd and non-systemd cases we could add
a second test to selftest instead which covers this?

Cheers,

Richard


  reply	other threads:[~2024-06-04 12:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 10:08 [PATCH] oeqa/runtime: fix regression in minidebuginfo test ecordonnier
2024-05-29 14:54 ` [OE-core] " Richard Purdie
2024-05-30 15:23   ` Etienne Cordonnier
     [not found]   ` <17D44D900E0F42D1.15404@lists.openembedded.org>
2024-06-03 11:35     ` Etienne Cordonnier
2024-06-03 11:42       ` Alexander Kanavin
2024-06-03 14:13       ` Richard Purdie
     [not found]       ` <17D5840BB429ED6B.21428@lists.openembedded.org>
2024-06-03 14:28         ` Richard Purdie
2024-06-04 11:45           ` Etienne Cordonnier
2024-06-04 11:56             ` Richard Purdie
2024-06-04 11:58               ` Etienne Cordonnier
2024-06-04 12:32                 ` Richard Purdie [this message]
2024-06-05 10:11                   ` Etienne Cordonnier

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=d3de56017f5df0786dc58d50308d9c76dfdd85cb.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ecordonnier@snap.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