From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 00/11] testing and configure updates
Date: Thu, 17 Dec 2020 23:41:58 +0000 [thread overview]
Message-ID: <87v9d0q9rr.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8SAGVe44y=6wHC_MxcmxUE=cSu5DGs-0Md3Zt+ZZrS+A@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Thu, 17 Dec 2020 at 09:43, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> The following changes since commit af3f37319cb1e1ca0c42842ecdbd1bcfc64a4b6f:
>>
>> Merge remote-tracking branch 'remotes/bonzini-gitlab/tags/for-upstream' into staging (2020-12-15 21:24:31 +0000)
>>
>> are available in the Git repository at:
>>
>> https://github.com/stsquad/qemu.git tags/pull-testing-171220-2
>>
>> for you to fetch changes up to a1c04860cec798914f8cd8ef77fce195f360d36e:
>>
>> tests: update for rename of CentOS8 PowerTools repo (2020-12-17 09:38:51 +0000)
>>
>> ----------------------------------------------------------------
>> Testing and configure updates:
>>
>> - add moxie-softmmu to deprecated_targets_list
>> - improve cross-build KVM coverage
>> - new --without-default-features configure flag
>> - add __repr__ for ConsoleSocket for debugging
>> - build tcg tests with -Werror
>> - test 32 bit builds with fedora
>> - remove last traces of debian9
>> - hotfix for centos8 powertools repo
>
> This seems to fail for x86 builds on my local Linux system with
> errors like this:
> make: Entering directory '/home/petmay01/linaro/qemu-for-merges/build/alldbg'
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
> QTEST_QEMU_IMG=./qemu-img
> G_TEST_DBUS_DAEMON=/home/petmay01/linaro/qemu-for-merges/tests/dbus-vmstate-daemon.sh
> QTEST_QEMU_BINARY=./qemu-system-moxie tests/qtest/qmp-cmd-test --tap
> -k
> sh: 1: exec: ./qemu-system-moxie: not found
> socket_accept failed: Resource temporarily unavailable
> **
> ERROR:../../tests/qtest/libqtest.c:308:qtest_init_without_qmp_handshake:
> assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
> ../../tests/qtest/libqtest.c:172: kill_qemu() tried to terminate QEMU
> process but encountered exit status 127 (expected 0)
> ERROR qtest-moxie/qmp-cmd-test - Bail out!
> ERROR:../../tests/qtest/libqtest.c:308:qtest_init_without_qmp_handshake:
> assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
> Makefile.mtest:2417: recipe for target 'run-test-300' failed
> make: *** [run-test-300] Error 1
> make: Leaving directory '/home/petmay01/linaro/qemu-for-merges/build/alldbg'
>
> Something in the Moxie deprecation patch not right?
> If we didn't build the executable we shouldn't try to
> run tests for it...
We shouldn't but I can't replicate the failure here. I'm guessing it
goes away on a "make clean"?
Maybe meson is leaving something behind from the previous iteration?
>
> thanks
> -- PMM
--
Alex Bennée
next prev parent reply other threads:[~2020-12-17 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 9:43 [PULL v2 00/11] testing and configure updates Alex Bennée
2020-12-17 18:48 ` Peter Maydell
2020-12-17 23:41 ` Alex Bennée [this message]
2020-12-18 11:12 ` Peter Maydell
2020-12-18 11:53 ` Alex Bennée
2020-12-18 13:40 ` Peter Maydell
2020-12-18 16:52 ` Alex Bennée
2020-12-18 17:17 ` Alex Bennée
2020-12-18 17:23 ` Paolo Bonzini
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=87v9d0q9rr.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).