From: Philippe Gerum <rpm@xenomai.org>
To: Tobias Schaffner <tobias.schaffner@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: [PATCH libevl] evl-test: return non-zero status when tests fail with -k
Date: Fri, 09 Jan 2026 17:06:26 +0100 [thread overview]
Message-ID: <87344ekby5.fsf@xenomai.org> (raw)
In-Reply-To: <20260109143157.1102568-1-tobias.schaffner@siemens.com> (Tobias Schaffner's message of "Fri, 9 Jan 2026 15:31:57 +0100")
Tobias Schaffner <tobias.schaffner@siemens.com> writes:
> The -k option of evl-test allows the test suite to continue running
> after a test failure. However, evl-test currently exits with status 0
> even if one or more tests have failed.
>
> Track the failure status and return a non-zero exit code when any test
> failed.
>
> Signed-off-by: Tobias Schaffner <tobias.schaffner@siemens.com>
> ---
> utils/evl-test | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/utils/evl-test b/utils/evl-test
> index b2d3a7f..0d0ca81 100644
> --- a/utils/evl-test
> +++ b/utils/evl-test
> @@ -68,6 +68,8 @@ if test x$do_list = xtrue; then
> exit 0
> fi
>
> +result=0
> +
> for t in $test_list; do
> test \! -x $t && echo "$(basename $0): $(basename $t): no such test" && exit 2
> # Swap stdout<->stderr for the test, capturing stderr into $log.
> @@ -83,9 +85,10 @@ for t in $test_list; do
> echo "$(basename $t): no kernel support"
> else
> echo "** $(basename $t): BROKEN"
> - test x$keep_going = xfalse && exit $status
> + result=$status
> + test x$keep_going = xfalse && break
> fi
> fi
> done
>
> -exit 0
> +exit $result
Merged, thanks.
--
Philippe.
prev parent reply other threads:[~2026-01-09 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 14:31 [PATCH libevl] evl-test: return non-zero status when tests fail with -k Tobias Schaffner
2026-01-09 16:06 ` Philippe Gerum [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=87344ekby5.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=tobias.schaffner@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 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.