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 5/6] grub-shell: Add halt_cmd variable to testcase namespace
Date: Tue, 10 Jan 2023 16:08:59 -0600 [thread overview]
Message-ID: <20230110220900.1248367-6-development@efficientek.com> (raw)
In-Reply-To: <20230110220900.1248367-1-development@efficientek.com>
This allows test case scripts to use the appropriate halt command for the
built architecture to end execution early. Otherwise, test case scripts
have no way to know the appropriate mechanism for halting the test case
early.
Signed-off-by: Glenn Washburn <development@efficientek.com>
---
tests/util/grub-shell.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/util/grub-shell.in b/tests/util/grub-shell.in
index f41e1a0b68..8db6ba86ec 100644
--- a/tests/util/grub-shell.in
+++ b/tests/util/grub-shell.in
@@ -331,6 +331,8 @@ fi
cfgfile="$work_directory/grub.cfg"
cat <<EOF >${cfgfile}
grubshell=yes
+halt_cmd=${halt_cmd}
+export halt_cmd
enable_progress_indicator=0
export enable_progress_indicator
EOF
--
2.34.1
next prev 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 ` [PATCH 4/6] grub-shell: Trim line should always be matched from the beginning of the line Glenn Washburn
2023-01-10 22:08 ` Glenn Washburn [this message]
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-6-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.