From: Richard Weinberger <richard@nod.at>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [PATCH 0/6] Revive alchemy tests
Date: Wed, 13 Apr 2022 16:14:01 +0200 (CEST) [thread overview]
Message-ID: <529434956.250361.1649859241634.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <1e9b7d24-a1db-7849-568d-36756584570a@siemens.com>
----- Ursprüngliche Mail -----
> Von: "Jan Kiszka" <jan.kiszka@siemens.com>
> An: "richard" <richard@nod.at>, "xenomai" <xenomai@xenomai.org>
> Gesendet: Mittwoch, 13. April 2022 14:56:16
> Betreff: Re: [PATCH 0/6] Revive alchemy tests
> On 08.04.22 10:03, Richard Weinberger via Xenomai wrote:
>> This patch series is a first attempt to integrate the currently abandoned
>> alchemy tests into Xenomai's test suite.
>> Since each test assumes running as own process a test driver is needed
>> which executes each tests separately.
>> The driver makes use of the smokey framework.
>>
>
> A valuable step forward. Just wondering, before actually taking it, if
> that can be a pattern for the rest as well (psos, vxworks) or if there
> is anything that should be considered in addition to allow them
> following later on.
I think the same approach will work for psos and vxworks too.
If you're fine with the proposed approach I'd prepare a v2 of this series
with psos and vxworks included.
Thanks,
//richard
next prev parent reply other threads:[~2022-04-13 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 8:03 [PATCH 0/6] Revive alchemy tests Richard Weinberger
2022-04-08 8:03 ` [PATCH 1/6] testsuite: Move alchemy tests into testsuite/ Richard Weinberger
2022-04-08 8:03 ` [PATCH 2/6] testsuite: Hook up alchemytests Richard Weinberger
2022-04-14 11:12 ` Jan Kiszka
2022-04-14 11:17 ` Richard Weinberger
2022-04-14 11:27 ` Jan Kiszka
2022-04-14 11:32 ` Richard Weinberger
2022-04-08 8:03 ` [PATCH 3/6] testsuite: Add a simple test driver for alchemytests Richard Weinberger
2022-04-08 9:11 ` Bezdeka, Florian
2022-04-08 9:19 ` Richard Weinberger
2022-04-08 10:34 ` Philippe Gerum
2022-04-08 10:49 ` Richard Weinberger
2022-04-08 12:01 ` Philippe Gerum
2022-04-08 12:11 ` Richard Weinberger
2022-04-08 8:03 ` [PATCH 4/6] Remove old alchemy tests Makefile Richard Weinberger
2022-04-08 8:04 ` [PATCH 5/6] alchemytests: Fix gcc warning in buffer-1 Richard Weinberger
2022-04-08 8:04 ` [PATCH 6/6] alchemytests: Fix gcc warning in task-9 Richard Weinberger
2022-04-13 12:56 ` [PATCH 0/6] Revive alchemy tests Jan Kiszka
2022-04-13 14:14 ` Richard Weinberger [this message]
2022-04-13 18:58 ` Jan Kiszka
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=529434956.250361.1649859241634.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.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 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.