From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: <qemu-devel@nongnu.org>
Cc: peter.maydell@linaro.org, dgilbert@redhat.com,
arei.gonglei@huawei.com, huangzhichao@huawei.com,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [RFC] cpus: avoid get stuck in pause_all_vcpus
Date: Tue, 10 Mar 2020 20:09:26 +0800 [thread overview]
Message-ID: <fed91a01-c545-bcfa-7215-36d69ab0f2ac@huawei.com> (raw)
In-Reply-To: <158383564824.20878.9634431361481694557@39012742ff91>
在 2020/3/10 18:20, no-reply@patchew.org 写道:
> Patchew URL: https://patchew.org/QEMU/20200310091443.1326-1-longpeng2@huawei.com/
>
>
>
> Hi,
>
> This series failed the asan build test. Please find the testing commands and
> their output below. If you have Docker installed, you can probably reproduce it
> locally.
>
Hi guys,
It seems this failure is NOT caused by my patch, so let's ignore it for the
moment...
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/wdt_ib700-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="wdt_ib700-test"
> PASS 1 wdt_ib700-test /x86_64/wdt_ib700/pause
> ---
> dbus-daemon[8273]: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry
>
> **
> ERROR:/tmp/qemu-test/src/tests/qtest/dbus-vmstate-test.c:114:get_connection: assertion failed (err == NULL): The connection is closed (g-io-error-quark, 18)
> ERROR - Bail out! ERROR:/tmp/qemu-test/src/tests/qtest/dbus-vmstate-test.c:114:get_connection: assertion failed (err == NULL): The connection is closed (g-io-error-quark, 18)
> cleaning up pid 8273
> make: *** [/tmp/qemu-test/src/tests/Makefile.include:632: check-qtest-x86_64] Error 1
> make: *** Waiting for unfinished jobs....
> Traceback (most recent call last):
> File "./tests/docker/docker.py", line 664, in <module>
> ---
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=88af8ba44214464d881ef7c7786167f4', '-u', '1003', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=x86_64-softmmu', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew2/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-a0j9h14_/src/docker-src.2020-03-10-05.52.52.1292:/var/tmp/qemu:z,ro', 'qemu:fedora', '/var/tmp/qemu/run', 'test-debug']' returned non-zero exit status 2.
> filter=--filter=label=com.qemu.instance.uuid=88af8ba44214464d881ef7c7786167f4
> make[1]: *** [docker-run] Error 1
> make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-a0j9h14_/src'
> make: *** [docker-run-test-debug@fedora] Error 2
>
> real 27m55.506s
> user 0m8.248s
>
>
> The full log is available at
> http://patchew.org/logs/20200310091443.1326-1-longpeng2@huawei.com/testing.asan/?type=message.
> ---
> Email generated automatically by Patchew [https://patchew.org/].
> Please send your feedback to patchew-devel@redhat.com
>
--
Regards,
Longpeng(Mike)
next prev parent reply other threads:[~2020-03-10 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 9:14 [RFC] cpus: avoid get stuck in pause_all_vcpus Longpeng(Mike)
2020-03-10 10:20 ` no-reply
2020-03-10 12:09 ` Longpeng (Mike) [this message]
2020-03-12 15:28 ` Paolo Bonzini
2020-03-13 1:43 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-03-13 7:09 ` Paolo Bonzini
2020-03-13 8:36 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-03-13 9:22 ` Paolo Bonzini
2020-03-13 9:41 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
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=fed91a01-c545-bcfa-7215-36d69ab0f2ac@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=huangzhichao@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).