From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, Henry Wang <Henry.Wang@arm.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 2/5] automation: hide timeout countdown in log
Date: Thu, 19 Oct 2023 00:16:31 +0200 [thread overview]
Message-ID: <ZTBZQGS91FfSeClt@mail-itl> (raw)
In-Reply-To: <9bcd8476-2a3f-43a3-8576-1e31d0df4bd3@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
On Wed, Oct 18, 2023 at 06:45:03PM +0100, Andrew Cooper wrote:
> On 06/10/2023 3:05 am, Marek Marczykowski-Górecki wrote:
> > grep+sleep message every 1s makes job log unnecessary hard to read.
> >
> > Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> > ---
> > I know I can download serial log file, but that's 3 more clicks...
> > ---
> > automation/scripts/qubes-x86-64.sh | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/automation/scripts/qubes-x86-64.sh b/automation/scripts/qubes-x86-64.sh
> > index 1e84e40a4afc..5464d10fc343 100755
> > --- a/automation/scripts/qubes-x86-64.sh
> > +++ b/automation/scripts/qubes-x86-64.sh
> > @@ -222,10 +222,12 @@ if [ -n "$wait_and_wakeup" ]; then
> > ssh $CONTROLLER wake
> > fi
> >
> > +set +x
> > until grep "^Welcome to Alpine Linux" smoke.serial || [ $timeout -le 0 ]; do
> > sleep 1;
> > : $((--timeout))
> > done
> > +set -x
> >
> > tail -n 100 smoke.serial
> >
>
> This wants repeating in dom0_check= when looking for "Welcome to Alpine"
> in guest-domU.log because the scrool is still visible in
>
> https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/5235487317
>
> Happy to fix on commit, as this is the only comment I have on the series.
Fine with me, thanks!
> Alternatively, would it be worth writing a "wait_until $msg $file"
> function to abstract this away?
Can refactor it later, maybe when adding more tests.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-18 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 2:05 [PATCH 0/5] automation: cleanup hardware based tests Marek Marczykowski-Górecki
2023-10-06 2:05 ` [PATCH 1/5] automation: include real-time view of the domU console log too Marek Marczykowski-Górecki
2023-10-06 2:05 ` [PATCH 2/5] automation: hide timeout countdown in log Marek Marczykowski-Górecki
2023-10-18 17:45 ` Andrew Cooper
2023-10-18 22:16 ` Marek Marczykowski-Górecki [this message]
2023-10-06 2:05 ` [PATCH 3/5] automation: cleanup test alpine install Marek Marczykowski-Górecki
2023-10-06 2:05 ` [PATCH 4/5] automation: improve checking for MSI/MSI-X in PCI passthrough tests Marek Marczykowski-Górecki
2023-10-18 23:30 ` Andrew Cooper
2023-10-19 0:16 ` Marek Marczykowski-Górecki
2023-10-06 2:05 ` [PATCH 5/5] automation: extract QEMU log in relevant hardware tests Marek Marczykowski-Górecki
2023-10-18 17:46 ` [PATCH for-4.18 0/5] automation: cleanup hardware based tests Andrew Cooper
2023-10-18 22:32 ` Stefano Stabellini
2023-10-19 0:31 ` Henry Wang
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=ZTBZQGS91FfSeClt@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=sstabellini@kernel.org \
--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.