From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [PATCH] test: directly exit when barebox state transition fails
Date: Fri, 23 Aug 2024 10:04:27 +0200 [thread overview]
Message-ID: <172440026763.2119534.18111451417132256941.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240822191714.3768641-1-a.fatoum@pengutronix.de>
On Thu, 22 Aug 2024 21:17:14 +0200, Ahmad Fatoum wrote:
> For trivial errors like a QEMU -bios or -kernel option not pointing at
> an existing file, the pytest output is extremely confusing. It prints a
> stack trace for every single test after QMPError("Received empty response")
> is raised and the stderr text explaining that the file is missing is
> easily overlooked.
>
> Improve this by just existing right away once a strategy transition
> fails and print the standard error if any as part of the exit message.
>
> [...]
Applied, thanks!
[1/1] test: directly exit when barebox state transition fails
https://git.pengutronix.de/cgit/barebox/commit/?id=acc33c6ca05e (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-08-23 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 19:17 Ahmad Fatoum
2024-08-23 8:04 ` Sascha Hauer [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=172440026763.2119534.18111451417132256941.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=bst@pengutronix.de \
/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