From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: naftaly.ralamboarivony@smile.fr,
openembedded-core@lists.openembedded.org,
Trevor Gamblin <tgamblin@baylibre.com>
Subject: Re: [OE-core][PATCH 1/3] patchtest: add --error-on-failure option
Date: Thu, 19 Mar 2026 17:22:08 +0000 [thread overview]
Message-ID: <e19c06100adcdf3d6dd18f7fe1e4201ea3cac494.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260318161209.54396-1-naftaly.ralamboarivony@smile.fr>
On Wed, 2026-03-18 at 17:12 +0100, naftaly.ralamboarivony via lists.openembedded.org wrote:
> From: Naftaly RALAMBOARIVONY <naftaly.ralamboarivony@smile.fr>
>
> Add a command line option to make patchtest return a non-zero exit
> status when a test fails.
>
> This keeps the current default behavior unchanged while allowing calling
> scripts and shells to detect test failures through the process exit
> status when explicitly requested.
Is there anywhere we rely on the current behaviour?
I'm wondering if we shouldn't just change the existing behaviour?
I'm not against an option but adding complexity if we don't need it and
can just change the behaviour might be preferable...
Cheers,
Richard
prev parent reply other threads:[~2026-03-19 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 16:12 [OE-core][PATCH 1/3] patchtest: add --error-on-failure option naftaly.ralamboarivony
2026-03-18 16:12 ` [OE-core][PATCH 2/3] patchtest/selftest: allow passing extra arguments to patchtest naftaly.ralamboarivony
2026-03-18 16:12 ` [OE-core][PATCH 3/3] patchtest/selftest: add test case for --error-on-failure return code naftaly.ralamboarivony
2026-03-19 17:22 ` Richard Purdie [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=e19c06100adcdf3d6dd18f7fe1e4201ea3cac494.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=naftaly.ralamboarivony@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=tgamblin@baylibre.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