From: no-reply@patchew.org
To: andrew@aj.id.au
Cc: peter.maydell@linaro.org, andrew@aj.id.au, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, joel@jms.id.au, clg@kaod.org
Subject: Re: [Qemu-devel] [PATCH v3] target-arm: Make the counter tick relative to cntfrq
Date: Tue, 10 Sep 2019 23:10:47 -0700 (PDT) [thread overview]
Message-ID: <156818224605.15929.1567552683650395230@5dec9699b7de> (raw)
In-Reply-To: <20190911034302.29108-1-andrew@aj.id.au>
Patchew URL: https://patchew.org/QEMU/20190911034302.29108-1-andrew@aj.id.au/
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 ===
libudev no
default devices yes
warning: Python 2 support is deprecated
warning: Python 3 will be required for building future versions of QEMU
NOTE: cross-compilers enabled: 'cc'
GEN x86_64-softmmu/config-devices.mak.tmp
---
qemu-system-aarch64: Invalid CNTFRQ: 0Hz
Broken pipe
/tmp/qemu-test/src/tests/libqtest.c:135: kill_qemu() tried to terminate QEMU process but encountered exit status 1
ERROR - too few tests run (expected 61, got 0)
make: *** [check-qtest-aarch64] Error 1
make: *** Waiting for unfinished jobs....
Could not access KVM kernel module: No such file or directory
The full log is available at
http://patchew.org/logs/20190911034302.29108-1-andrew@aj.id.au/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2019-09-11 6:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 3:43 [Qemu-devel] [PATCH v3] target-arm: Make the counter tick relative to cntfrq Andrew Jeffery
2019-09-11 6:10 ` no-reply [this message]
2019-09-11 12:44 ` Andrew Jeffery
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=156818224605.15929.1567552683650395230@5dec9699b7de \
--to=no-reply@patchew.org \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 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.