From: Roger Pau Monne <roger.pau@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Doug Goldstein <cardoe@cardoe.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH 1/2] automation: add timestamps to Xen tests
Date: Tue, 3 Dec 2019 11:33:51 +0100 [thread overview]
Message-ID: <20191203103352.29728-2-roger.pau@citrix.com> (raw)
In-Reply-To: <20191203103352.29728-1-roger.pau@citrix.com>
Enable Xen timestamps in the automated Xen tests, this is helpful in
order to figure out if Xen is stuck or just slow in the automated
tests.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
automation/scripts/qemu-smoke-x86-64.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/automation/scripts/qemu-smoke-x86-64.sh b/automation/scripts/qemu-smoke-x86-64.sh
index 5fa3a63dbd..f38eacfd9f 100755
--- a/automation/scripts/qemu-smoke-x86-64.sh
+++ b/automation/scripts/qemu-smoke-x86-64.sh
@@ -24,7 +24,8 @@ set +e
timeout -k 1 10 \
qemu-system-x86_64 -nographic -kernel binaries/xen \
-initrd xtf/tests/example/$k \
- -append "loglvl=all com1=115200,,8n1 console=com1 noreboot $extra" \
+ -append "loglvl=all com1=115200,,8n1 console=com1 noreboot \
+ console_timestamps=boot $extra" \
-m 512 -monitor none -serial file:smoke.serial
set -e
grep -q 'Test result: SUCCESS' smoke.serial || exit 1
--
2.24.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-03 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 10:33 [Xen-devel] [PATCH 0/2] automation: improve tests Roger Pau Monne
2019-12-03 10:33 ` Roger Pau Monne [this message]
2019-12-03 11:24 ` [Xen-devel] [PATCH 1/2] automation: add timestamps to Xen tests Wei Liu
2019-12-03 10:33 ` [Xen-devel] [PATCH 2/2] automation: increase tests maximum time from 10s to 30s Roger Pau Monne
2019-12-03 11:23 ` Wei Liu
2019-12-03 10:37 ` [Xen-devel] [PATCH 0/2] automation: improve tests Andrew Cooper
2019-12-03 13:20 ` Jürgen Groß
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=20191203103352.29728-2-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=cardoe@cardoe.com \
--cc=xen-devel@lists.xenproject.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 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.