From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: peter.maydell@linaro.org, sstabellini@kernel.org,
qemu-trivial@nongnu.org, mjt@tls.msk.ru, qemu-devel@nongnu.org,
laurent@vivier.eu, marcandre.lureau@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>,
david@gibson.dropbear.id.au
Subject: Re: [PATCH] global: Squash 'the the'
Date: Tue, 5 Nov 2019 12:13:59 +0000 [thread overview]
Message-ID: <20191105121359.GA2781@work-vm> (raw)
In-Reply-To: <b0d5498a-1ee3-3bea-43f3-4d4d8397711a@redhat.com>
* Laurent Vivier (lvivier@redhat.com) wrote:
> On 05/11/2019 09:16, Alex Bennée wrote:
> >
> > no-reply@patchew.org writes:
> >
> >> Patchew URL: https://patchew.org/QEMU/20191104185202.102504-1-dgilbert@redhat.com/
> >>
> >>
> >>
> >> Hi,
> >>
> >> This series failed the docker-quick@centos7 build test. Please find the testing commands and
> >> their output below. If you have Docker installed, you can probably reproduce it
> >> locally.
> >>
> >> === TEST SCRIPT BEGIN ===
> >> #!/bin/bash
> >> make docker-image-centos7 V=1 NETWORK=1
> >> time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1
> >> === TEST SCRIPT END ===
> >>
> >> TEST iotest-qcow2: 009
> >> TEST iotest-qcow2: 010
> >> **
> >> ERROR:/tmp/qemu-test/src/tests/migration-test.c:903:wait_for_migration_fail: assertion failed: (!strcmp(status, "setup") || !strcmp(status, "failed") || (allow_active && !strcmp(status, "active")))
> >> ERROR - Bail out! ERROR:/tmp/qemu-test/src/tests/migration-test.c:903:wait_for_migration_fail: assertion failed: (!strcmp(status, "setup") || !strcmp(status, "failed") || (allow_active && !strcmp(status, "active")))
> >> make: *** [check-qtest-aarch64] Error 1
> >> make: *** Waiting for unfinished jobs....
> >
> > That's one I've been seeing intermittently on Travis since the
> > softfreeze started. It was masked by the other regressions which are now
> > fixed.
>
> Could it be related with my patch?
>
> 1bd71dce4bf2 runstate: ignore exit request in finish migrate state
Possible but unlikely I think; lets see if I can reproduce it and get a
backtrace; (It would be very nice if I could get that assertion to tell
me what 'status' is; we know it's not setup or failed, and it may or may
not be active; but what it is ....well that's anyones guess.
Dave
> Thanks,
> Laurent
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-11-05 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 18:52 [PATCH] global: Squash 'the the' Dr. David Alan Gilbert (git)
2019-11-04 20:03 ` Alex Bennée
2019-11-04 20:27 ` Laurent Vivier
2019-11-04 21:40 ` no-reply
2019-11-04 21:54 ` Philippe Mathieu-Daudé
2019-11-05 8:16 ` Alex Bennée
2019-11-05 8:40 ` Laurent Vivier
2019-11-05 12:13 ` Dr. David Alan Gilbert [this message]
2019-11-05 18:57 ` Dr. David Alan Gilbert
2019-11-04 23:22 ` no-reply
2019-11-05 14:06 ` Laurent Vivier
2019-11-06 21:12 ` David Gibson
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=20191105121359.GA2781@work-vm \
--to=dgilbert@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=laurent@vivier.eu \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sstabellini@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).