From: Aaron Marcher <aaron@sigma-star.at>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: [PATCH 0/6] Minor testsuite cleanups
Date: Fri, 3 Nov 2023 15:36:29 +0100 [thread overview]
Message-ID: <20231103143629.j4mk6qihavilejdm@mail> (raw)
In-Reply-To: <20231030-flo-cleanup-testsuite-v1-0-0fb7bbd2d45f@siemens.com>
Hi Florian,
thanks for the cleanups on my changes.
Reviewed-by: Aaron Marcher <aaron@sigma-star.at>
Best regards,
Aaron
--
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y
On Thu, Nov 02, 2023 at 03:41:41PM +0100, Florian Bezdeka wrote:
> Hi all,
>
> this is the result of the analysis of our recent CI logs. Seems that we
> did not properly report failing tests and continued with test execution,
> hiding some real (but still minor) issues.
>
> Best regards,
> Florian
>
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> ---
> Florian Bezdeka (6):
> testsuite: vxworkstests: Do not try to call nonexistent binary
> testsuite: smokey: Refactor smokey_run_extprog()
> testsuite: smokey/spitest: Fix --keep-going in combination with --verbose
> testsuite: alchemytests: Skip pipe test if kernel support is missing
> testsuite: vxworkstests: Skip tests if low resolution clock not enabled
> testsuite: psostests: Skip tests if low resolution clock not enabled
>
> include/smokey/smokey.h | 3 +-
> lib/smokey/helpers.c | 14 +++-
> testsuite/smokey/alchemytests/alchemytests.c | 74 +++++++++---------
> testsuite/smokey/alchemytests/pipe-1.c | 8 +-
> testsuite/smokey/main.c | 5 +-
> testsuite/smokey/psostests/psostests.c | 109 +++++++++++++--------------
> testsuite/smokey/vxworkstests/vxworkstests.c | 64 ++++++++--------
> testsuite/spitest/spitest.c | 5 +-
> 8 files changed, 142 insertions(+), 140 deletions(-)
> ---
> base-commit: 14470d7d58dbfe7210cfa93f03e241a38d9fa798
> change-id: 20231030-flo-cleanup-testsuite-bc6ea7f6dc31
>
> Best regards,
> --
> Florian Bezdeka <florian.bezdeka@siemens.com>
prev parent reply other threads:[~2023-11-03 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 14:41 [PATCH 0/6] Minor testsuite cleanups Florian Bezdeka
2023-11-02 14:41 ` [PATCH 1/6] testsuite: vxworkstests: Do not try to call nonexistent binary Florian Bezdeka
2023-11-02 14:41 ` [PATCH 2/6] testsuite: smokey: Refactor smokey_run_extprog() Florian Bezdeka
2023-11-02 14:54 ` Jan Kiszka
2023-11-02 14:41 ` [PATCH 3/6] testsuite: smokey/spitest: Fix --keep-going in combination with --verbose Florian Bezdeka
2023-11-02 14:41 ` [PATCH 4/6] testsuite: alchemytests: Skip pipe test if kernel support is missing Florian Bezdeka
2023-11-02 14:56 ` Jan Kiszka
2023-11-03 10:45 ` Florian Bezdeka
2023-11-02 14:41 ` [PATCH 5/6] testsuite: vxworkstests: Skip tests if low resolution clock not enabled Florian Bezdeka
2023-11-02 14:41 ` [PATCH 6/6] testsuite: psostests: " Florian Bezdeka
2023-11-02 15:07 ` [PATCH 0/6] Minor testsuite cleanups Jan Kiszka
2023-11-03 14:36 ` Aaron Marcher [this message]
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=20231103143629.j4mk6qihavilejdm@mail \
--to=aaron@sigma-star.at \
--cc=florian.bezdeka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).