From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] test: py: network: await prompt after ctrl+c
Date: Thu, 26 Feb 2026 13:14:23 +0100 [thread overview]
Message-ID: <177210806368.2186588.13500727787857098039.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260225141536.258005-1-a.fatoum@pengutronix.de>
On Wed, 25 Feb 2026 15:15:34 +0100, Ahmad Fatoum wrote:
> The expect buffer will contain the <INTERRUPT> string output by barebox
> followed by a prompt, which run_check would gobble up.
>
> Currently, this doesn't matter, but when we start to additionally match
> against the plain prompt, this would lead us not to match the prompt
> string with the marker in run_check.
> To fix this, _await_prompt to get the <INTERRUPT><prompt> removed from
> the expect buffer.
>
> [...]
Applied, thanks!
[1/1] test: py: network: await prompt after ctrl+c
https://git.pengutronix.de/cgit/barebox/commit/?id=ca40477c067d (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-02-26 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 14:15 Ahmad Fatoum
2026-02-26 12:14 ` 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=177210806368.2186588.13500727787857098039.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox