From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH] tests: Disable dbus-vmstate-test
Date: Tue, 10 Mar 2020 16:26:55 +0100 [thread overview]
Message-ID: <99854e03-fe9e-e6a9-d9ba-3abf8d9acf98@redhat.com> (raw)
In-Reply-To: <20200310152141.13959-1-peter.maydell@linaro.org>
On 10/03/20 16:21, Peter Maydell wrote:
>
> dbus-daemon[9321]: 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)
> cleaning up pid 9321
> 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)
> make: *** [/tmp/qemu-test/src/tests/Makefile.include:632: check-qtest-x86_64] Error 1
> make: *** Waiting for unfinished jobs....
>
> It's not clear why this is happening (perhaps a recently revealed
> race condition or a change in the patchew build environment?).
>
> For the moment, disable this test so that patchew test runs are
> useful and don't email the list with spurious failure mails.
It has failed forever since it has been committed. It only happens in
the Ubuntu configuration, and I had disabled it for a long time due to
this failure. On March 6th I added it back to see if someone had fixed it.
Paolo
next prev parent reply other threads:[~2020-03-10 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 15:21 [PATCH] tests: Disable dbus-vmstate-test Peter Maydell
2020-03-10 15:26 ` Paolo Bonzini [this message]
2020-03-10 21:53 ` Marc-André Lureau
2020-03-10 15:27 ` Laurent Vivier
2020-03-12 14:47 ` Peter Maydell
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=99854e03-fe9e-e6a9-d9ba-3abf8d9acf98@redhat.com \
--to=pbonzini@redhat.com \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.