All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org, Daniel Kiper <dkiper@net-space.pl>
Cc: Patrick Steinhardt <ps@pks.im>,
	Glenn Washburn <development@efficientek.com>
Subject: [PATCH 4/6] grub-shell: Trim line should always be matched from the beginning of the line
Date: Tue, 10 Jan 2023 16:08:58 -0600	[thread overview]
Message-ID: <20230110220900.1248367-5-development@efficientek.com> (raw)
In-Reply-To: <20230110220900.1248367-1-development@efficientek.com>

When turning on shell tracing the trim line will be output before we
actually want to start the trim. However, in this case the trim line never
starts from the beginning of the line. So start trimming from the correct
line by matching from the beginning of the line.

Signed-off-by: Glenn Washburn <development@efficientek.com>
---
 tests/util/grub-shell.in | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/util/grub-shell.in b/tests/util/grub-shell.in
index 585f0d066e..f41e1a0b68 100644
--- a/tests/util/grub-shell.in
+++ b/tests/util/grub-shell.in
@@ -360,7 +360,7 @@ terminal_output ${term}
 EOF
 
 if [ $trim = 1 ]; then
-    echo "echo $trim_head" >>${cfgfile}
+    echo "echo; echo $trim_head" >>${cfgfile}
 fi
 
 rom_directory="$work_directory/rom_directory"
@@ -484,7 +484,7 @@ fi
 do_trim ()
 {
     if [ $trim = 1 ] || [ $trim = 2 ]; then
-	awk '{ if (have_head == 1) print $0; } /'"$trim_head"'/ { have_head=1; }'
+	awk '{ if (have_head == 1) print $0; } /^'"$trim_head"'/ { have_head=1; }'
     else
 	cat
     fi
-- 
2.34.1



  parent reply	other threads:[~2023-01-10 22:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 22:08 [PATCH 0/6] Cryptomount testing Glenn Washburn
2023-01-10 22:08 ` [PATCH 1/6] grub-shell: Set exit status to qemu exit status Glenn Washburn
2023-01-10 22:08 ` [PATCH 2/6] grub-shell: Only cleanup working directory file if QEMU does not fail or timeout Glenn Washburn
2023-01-10 22:08 ` [PATCH 3/6] grub-shell: Allow specifying non-default trim line contents Glenn Washburn
2023-01-10 22:08 ` Glenn Washburn [this message]
2023-01-10 22:08 ` [PATCH 5/6] grub-shell: Add halt_cmd variable to testcase namespace Glenn Washburn
2023-01-10 22:09 ` [PATCH 6/6] tests: Add cryptomount functional test Glenn Washburn
2023-01-12 16:23 ` [PATCH 0/6] Cryptomount testing Daniel Kiper
2023-01-13  8:13   ` Patrick Steinhardt

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=20230110220900.1248367-5-development@efficientek.com \
    --to=development@efficientek.com \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=ps@pks.im \
    /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.