qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PULL 0/9] Testing patches
Date: Fri, 26 Oct 2018 22:15:20 +0800	[thread overview]
Message-ID: <20181026141529.4305-1-famz@redhat.com> (raw)

The following changes since commit 808ebd66e467f77c0d1f8c6346235f81e9c99cf2:

  Merge remote-tracking branch 'remotes/riscv/tags/riscv-for-master-3.1-sf0' into staging (2018-10-25 17:41:03 +0100)

are available in the Git repository at:

  git://github.com/famz/qemu.git tags/testing-pull-request

for you to fetch changes up to 63a24c5e2354833a84f18bdf0e857fad8812f65b:

  tests/vm: Do not abuse parallelism when HOST != TARGET architecture (2018-10-26 22:03:21 +0800)

----------------------------------------------------------------
Testing patches

One fix for mingw build and some improvements in VM based testing, many thanks
to Paolo and Phil.

----------------------------------------------------------------

Paolo Bonzini (1):
  tests: docker: update test-mingw for GTK+ 2.0 removal

Philippe Mathieu-Daudé (8):
  tests/vm: Extract the kvm_available() handy function
  tests/vm: Do not abuse parallelism when KVM is not available
  tests/vm: Do not use the -smp option with a single cpu
  tests/vm: Display remaining seconds to wait for a VM to start
  tests/vm: Add a BaseVM::arch property
  tests/vm: Let kvm_available() work in cross environments
  tests/vm: Do not use -enable-kvm if HOST != TARGET architecture
  tests/vm: Do not abuse parallelism when HOST != TARGET architecture

 scripts/qemu.py         |  6 ++++++
 tests/docker/test-mingw |  3 +--
 tests/vm/basevm.py      | 30 +++++++++++++++++++++---------
 tests/vm/centos         |  1 +
 tests/vm/freebsd        |  1 +
 tests/vm/netbsd         |  1 +
 tests/vm/openbsd        |  1 +
 tests/vm/ubuntu.i386    |  1 +
 8 files changed, 33 insertions(+), 11 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-10-26 14:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 14:15 Fam Zheng [this message]
2018-10-26 14:15 ` [Qemu-devel] [PULL 1/9] tests: docker: update test-mingw for GTK+ 2.0 removal Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 2/9] tests/vm: Extract the kvm_available() handy function Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 3/9] tests/vm: Do not abuse parallelism when KVM is not available Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 4/9] tests/vm: Do not use the -smp option with a single cpu Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 5/9] tests/vm: Display remaining seconds to wait for a VM to start Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 6/9] tests/vm: Add a BaseVM::arch property Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 7/9] tests/vm: Let kvm_available() work in cross environments Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 8/9] tests/vm: Do not use -enable-kvm if HOST != TARGET architecture Fam Zheng
2018-10-26 14:15 ` [Qemu-devel] [PULL 9/9] tests/vm: Do not abuse parallelism when " Fam Zheng
2018-10-29 10:22 ` [Qemu-devel] [PULL 0/9] Testing patches 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=20181026141529.4305-1-famz@redhat.com \
    --to=famz@redhat.com \
    --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).