From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.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 14:06:14 +0800 [thread overview]
Message-ID: <16a50e80-4e34-e7aa-016e-12e2b1d32958@windriver.com> (raw)
In-Reply-To: <6c04cfc3-2553-98ef-1b43-6a08a02d9e9a@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
On 03/19/2018 05:04 PM, Alexander Kanavin wrote:
> On 03/19/2018 06:53 AM, ChenQi wrote:
>
>> For autotools,
>> 1) if the test framework of some package is a standalone set of
>> scripts or it could be easily decoupled from Makefile, adding ptest
>> support for such package is easy.
>> 2) if the test framework of some package is coupled with Makefile, we
>> need to adjust or replace vars in Makefile, install make on target
>> and rely on the Makefile to run tests. In such case, adding ptest is
>> not easy.
>>
>> For meson, the test framework is coupled with meson/ninja. We need to
>> at least install ninja and meson on target as a first step. Maybe we
>> need to adjust other things in do_install_ptest. That's why I said
>> "there's no easy way to add ptest support."
>>
>> Why didn't I look further into this problem? Because I view ptest
>> support as optional, not necessary.
>> What I thought was: "let's upgrade the package first. If ptest
>> support is required from community, deal with that in a separate patch."
>>
>> Now that I've got feedback from you, I think I'll look further into
>> this issue and try to add ptest support via a separate patch.
>
> But is it tightly coupled with meson/ninja? From what I see here:
>
> https://github.com/systemd/systemd/blob/master/test/meson.build
>
> there is no testing logic as such in the meson.build file, it simply
> runs a few test scripts, and checks the outcome. Which we can easily
> replicate in a script.
>
> Alex
>
Hi Alex,
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.
Best Regards,
Chen Qi
[-- Attachment #2: Type: text/html, Size: 3750 bytes --]
next prev parent reply other threads:[~2018-03-22 6:05 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 [this message]
2018-03-22 11:14 ` Alexander Kanavin
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=16a50e80-4e34-e7aa-016e-12e2b1d32958@windriver.com \
--to=qi.chen@windriver.com \
--cc=alexander.kanavin@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.