From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Xiao Guangrong <xiaoguangrong@tencent.com>,
Paolo Bonzini <pbonzini@redhat.com>,
alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH] tests/docker: Refresh APT cache before installing new packages on Debian
Date: Wed, 24 Jul 2019 12:46:51 +0200 [thread overview]
Message-ID: <d4992f3d-489a-644e-093f-dfbff27bdda8@redhat.com> (raw)
In-Reply-To: <156390240449.12764.14466682904037881386@c4a48874b076>
Cc'ing the qtest maintainers and Xiao since I have no clue about this test.
On 7/23/19 7:20 PM, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20190723141528.18023-1-philmd@redhat.com/
> ---
> PASS 4 pxe-test /x86_64/pxe/ipv4/q35/virtio-net-pci
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/rtc-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="rtc-test"
> **
> ERROR:/tmp/qemu-test/src/tests/rtc-test.c:173:check_time: assertion failed (ABS(t - s) <= wiggle): (3 <= 2)
> ERROR - Bail out! ERROR:/tmp/qemu-test/src/tests/rtc-test.c:173:check_time: assertion failed (ABS(t - s) <= wiggle): (3 <= 2)
> make: *** [/tmp/qemu-test/src/tests/Makefile.include:899: check-qtest-x86_64] Error 1
> make: *** Waiting for unfinished jobs....
> Traceback (most recent call last):
>
> The full log is available at
> http://patchew.org/logs/20190723141528.18023-1-philmd@redhat.com/testing.asan/?type=message.
next prev parent reply other threads:[~2019-07-24 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 14:15 [Qemu-devel] [PATCH] tests/docker: Refresh APT cache before installing new packages on Debian Philippe Mathieu-Daudé
2019-07-23 17:20 ` no-reply
2019-07-24 10:46 ` Philippe Mathieu-Daudé [this message]
2019-07-24 11:25 ` Thomas Huth
2019-07-24 11:45 ` 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=d4992f3d-489a-644e-093f-dfbff27bdda8@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=xiaoguangrong@tencent.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;
as well as URLs for NNTP newsgroup(s).