From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oeqa/selftest/runtime_test: split systemd and sysvinit tests out
Date: Fri, 06 Dec 2019 14:44:07 +0000 [thread overview]
Message-ID: <6a80ccde7c8e45b32fe916fe66ca02f01388f4e1.camel@linuxfoundation.org> (raw)
In-Reply-To: <20191206015820.1839-1-akuster808@gmail.com>
On Thu, 2019-12-05 at 17:58 -0800, Armin Kuster wrote:
> This should help debug which part of this selftest is failing.
> We can not tell which outloop is failing so split the tests into
> systemd and sysvinit.
>
> See [Yocto # 13650] for more details.
>
> Signed-off-by: Armin Kuster <akuster808@gmail.com>
> ---
> meta/lib/oeqa/selftest/cases/runtime_test.py | 102 ++++++++++++++---
> --
> 1 file changed, 76 insertions(+), 26 deletions(-)
Rather than duplicating the code could we have a common function the
tests call please?
Cheers,
Richard
next prev parent reply other threads:[~2019-12-06 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 1:58 [PATCH] oeqa/selftest/runtime_test: split systemd and sysvinit tests out Armin Kuster
2019-12-06 14:44 ` Richard Purdie [this message]
2019-12-06 16:09 ` akuster808
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=6a80ccde7c8e45b32fe916fe66ca02f01388f4e1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.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