Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: ChenQi <Qi.Chen@windriver.com>,
	Randy MacLeod <randy.macleod@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] systemd: upgrade to 237
Date: Thu, 22 Mar 2018 13:14:56 +0200	[thread overview]
Message-ID: <bf908c93-3935-e053-e601-445400ff7ed4@linux.intel.com> (raw)
In-Reply-To: <16a50e80-4e34-e7aa-016e-12e2b1d32958@windriver.com>

On 03/22/2018 08:06 AM, ChenQi wrote:
> The test framework meson uses is like:
> 
> |e = executable('prog', 'testprog.c') test('name of test', e)|
> 
> 
> http://mesonbuild.com/Unit-tests.html
> 
> So they could be defined in any valid meson.build file. In systemd's 
> case, most of them are in top-level meson.build.
> 
> I agree with you that it's possible to extract all these test cases and 
> hold them in a custom script we write. I think this could serve as a 
> fall-back approach to adding ptest support for systemd.
> But I'd like to spend some time to try to find a more general approach, 
> avoiding headaches when upgrading.

That's right. We probably need to put some kind of 'hook' inside meson's 
test() that would copy the test case to a ptest directory, instead of 
running it.

Alex


  reply	other threads:[~2018-03-22 11:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12  8:38 [PATCH 0/3] systemd & systemd-boot: upgrade to 237 Chen Qi
2018-03-12  8:38 ` [PATCH 1/3] systemd: " Chen Qi
2018-03-12  8:52   ` Maxin B. John
2018-03-12  9:16     ` ChenQi
2018-03-16 19:30   ` Randy MacLeod
2018-03-16 19:27     ` Alexander Kanavin
2018-03-19  4:53       ` ChenQi
2018-03-19  5:21         ` Khem Raj
2018-03-19  9:04         ` Alexander Kanavin
2018-03-22  6:06           ` ChenQi
2018-03-22 11:14             ` Alexander Kanavin [this message]
2018-03-22 16:12               ` Randy MacLeod
2018-03-22 16:14                 ` Burton, Ross
2018-03-22 16:30                   ` Khem Raj
2018-03-20 17:19   ` Alex Kiernan
2018-03-20 17:36     ` Khem Raj
2018-03-20 18:00       ` Burton, Ross
2018-03-22  7:36         ` ChenQi
2018-03-12  8:38 ` [PATCH 2/3] systemd: fix build failure for qemux86 and qemuppc with musl Chen Qi
2018-03-12  8:38 ` [PATCH 3/3] systemd-boot: upgrade to 237 Chen Qi
2018-03-12  8:43 ` [PATCH 0/3] systemd & " ChenQi
2018-03-15  1:59 ` ChenQi
2018-03-15 10:51   ` Burton, Ross

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=bf908c93-3935-e053-e601-445400ff7ed4@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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