From: "Marc Hartmayer" <mhartmay@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>,
frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com,
npiggin@gmail.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v1] arch-run: Wait for incoming socket being removed
Date: Tue, 05 Mar 2024 19:12:16 +0100 [thread overview]
Message-ID: <87il20lf9b.fsf@linux.ibm.com> (raw)
In-Reply-To: <20240305141214.707046-1-nrb@linux.ibm.com>
On Tue, Mar 05, 2024 at 03:11 PM +0100, Nico Boehr <nrb@linux.ibm.com> wrote:
> Sometimes, QEMU needs a bit longer to remove the incoming migration
> socket. This happens in some environments on s390x for the
> migration-skey-sequential test.
>
> Instead of directly erroring out, wait for the removal of the socket.
>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> ---
> scripts/arch-run.bash | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/scripts/arch-run.bash b/scripts/arch-run.bash
> index 2214d940cf7d..413f3eda8cb8 100644
> --- a/scripts/arch-run.bash
> +++ b/scripts/arch-run.bash
> @@ -237,12 +237,8 @@ do_migration ()
> echo > ${dst_infifo}
> rm ${dst_infifo}
>
> - # Ensure the incoming socket is removed, ready for next destination
> - if [ -S ${dst_incoming} ] ; then
> - echo "ERROR: Incoming migration socket not removed after migration." >& 2
> - qmp ${dst_qmp} '"quit"'> ${dst_qmpout} 2>/dev/null
> - return 2
> - fi
> + # Wait for the incoming socket being removed, ready for next destination
> + while [ -S ${dst_incoming} ] ; do sleep 0.1 ; done
But now, you have removed the erroring out path completely. Maybe wait
max. 3s and then bail out?
[…snip]
next prev parent reply other threads:[~2024-03-05 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 14:11 [kvm-unit-tests PATCH v1] arch-run: Wait for incoming socket being removed Nico Boehr
2024-03-05 18:12 ` Marc Hartmayer [this message]
2024-03-06 13:03 ` Nico Boehr
2024-03-12 5:39 ` Nicholas Piggin
2024-03-12 6:37 ` Nicholas Piggin
2024-03-12 6:45 ` Thomas Huth
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=87il20lf9b.fsf@linux.ibm.com \
--to=mhartmay@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=nrb@linux.ibm.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