From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Nico Boehr" <nrb@linux.ibm.com>, <kvm@vger.kernel.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>, "Thomas Huth" <thuth@redhat.com>
Subject: Re: [kvm-unit-tests PATCH 2/3] migration: Fix test harness hang if source does not reach migration point
Date: Sun, 30 Jul 2023 20:03:36 +1000 [thread overview]
Message-ID: <CUFF6E1RB78K.QT91UG08M495@wheely> (raw)
In-Reply-To: <169052965551.15205.2179571087904012453@t14-nrb>
On Fri Jul 28, 2023 at 5:34 PM AEST, Nico Boehr wrote:
> Quoting Nicholas Piggin (2023-07-25 05:39:36)
> > After starting the test, the harness waits polling for "migrate" in the
> > output. If the test does not print for some reason, the harness hangs.
> >
> > Test that the pid is still alive while polling to fix this hang.
> >
> > While here, wait for the full string "Now migrate the VM", which I think
> > makes it more obvious to read and could avoid an unfortunate collision
> > with some debugging output in a test case.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
>
> Thanks for attempting to fix this!
>
> > ---
> > scripts/arch-run.bash | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/scripts/arch-run.bash b/scripts/arch-run.bash
> > index 518607f4..30e535c7 100644
> > --- a/scripts/arch-run.bash
> > +++ b/scripts/arch-run.bash
> > @@ -142,6 +142,7 @@ run_migration ()
> >
> > eval "$@" -chardev socket,id=mon1,path=${qmp1},server=on,wait=off \
> > -mon chardev=mon1,mode=control | tee ${migout1} &
> > + live_pid=`jobs -l %+ | grep "eval" | awk '{print$2}'`
>
> Pardon my ignorance, but why would $! not work here?
My mastery of bash is poor, I copied the incoming_pid line. It seems
to work, but if you think $! is better I can try it.
Thanks,
Nick
next prev parent reply other threads:[~2023-07-30 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 3:39 [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration Nicholas Piggin
2023-07-25 3:39 ` [kvm-unit-tests PATCH 1/3] migration: Fix test harness hang on fifo Nicholas Piggin
2023-07-28 7:20 ` Nico Boehr
2023-07-25 3:39 ` [kvm-unit-tests PATCH 2/3] migration: Fix test harness hang if source does not reach migration point Nicholas Piggin
2023-07-28 7:34 ` Nico Boehr
2023-07-30 10:03 ` Nicholas Piggin [this message]
2023-09-25 11:14 ` Nico Boehr
2023-10-16 18:32 ` Thomas Huth
2023-10-19 7:55 ` Nico Boehr
2023-10-19 8:10 ` Thomas Huth
2023-07-25 3:39 ` [kvm-unit-tests PATCH 3/3] arch-run: Support multiple migrations Nicholas Piggin
2023-07-28 8:44 ` [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration Shaoqin Huang
2023-07-30 10:06 ` Nicholas Piggin
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=CUFF6E1RB78K.QT91UG08M495@wheely \
--to=npiggin@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=thuth@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox