From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] test: Make handling of shell prompts with escapes a little more reliable
Date: Thu, 7 Dec 2023 12:09:26 +1100 [thread overview]
Message-ID: <ZXEbRvVuxmKQ4QcL@zatzit> (raw)
In-Reply-To: <20231204105433.2a4df0d2@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]
On Mon, Dec 04, 2023 at 10:54:33AM +0100, Stefano Brivio wrote:
> On Thu, 23 Nov 2023 12:52:53 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > When using the old-style "pane" methods of executing commands during the
> > tests, we need to scan the shell output for prompts in order to tell when
> > commands have finished. This is inherently unreliable because commands
> > could output things that look like prompts, and prompts might not look like
> > we expect them to. The only way to really fix this is to use a better way
> > of dispatching commands, like the newer "context" system.
> >
> > However, it's awkward to convert everything to "context" right at the
> > moment, so we're still relying on some tests that do work most of the time.
> > It is, however, particularly sensitive to fancy coloured prompts using
> > escape sequences. Currently we try to handle this by stripping actual
> > ESC characters with tr, then looking for some common variants.
> >
> > We can do a bit better: instead strip all escape sequences using sed before
> > looking for our prompt. Or, at least, any one using [a-zA-Z] as the
> > terminating character. Strictly speaking ANSI escapes can be terminated by
> > any character in 0x40..0x7e, which isn't easily expressed in a regexp.
> > This should capture all common ones, though.
> >
> > With this transformation we can simplify the list of patterns we then look
> > for as a prompt, removing some redundant variants.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>
> I didn't forget about this one, but I had unrelated test failures which
> I wasn't sure about. This is actually fine though. Applying soon.
I don't think there's any particular need to make a release for it,
but it would be nice to get this in the main git tree, so I don't have
to keep awkwardly carrying it about to test my other branches.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-07 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 1:52 [PATCH] test: Make handling of shell prompts with escapes a little more reliable David Gibson
2023-12-04 9:54 ` Stefano Brivio
2023-12-07 1:09 ` David Gibson [this message]
2023-12-07 6:26 ` Stefano Brivio
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=ZXEbRvVuxmKQ4QcL@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).