From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 00/20] testing/next for 4.1
Date: Tue, 2 Jul 2019 11:25:05 +0100 [thread overview]
Message-ID: <20190702102505.32044-1-alex.bennee@linaro.org> (raw)
The following changes since commit 7d0e02405fc02a181319b1ab8681d2f72246b7c6:
Merge remote-tracking branch 'remotes/vivier2/tags/trivial-patches-pull-request' into staging (2019-07-01 17:40:32 +0100)
are available in the Git repository at:
https://github.com/stsquad/qemu.git tags/pull-testing-next-020719-2
for you to fetch changes up to 83fb8fd71de2f80afd4ec83761357d5f0dacd9c9:
migration: move port_attr inside CONFIG_LINUX (2019-07-02 07:52:35 +0100)
----------------------------------------------------------------
Various testing fixes:
- tests/vm updates and clean-ups
- tests/vm serial autobuild on host
- ensure MacOS builds do "brew update"
- ensure we test --static user builds
- fix hyperv compile failure
- fix missing var warning for OpenBSD (v2)
This brings my testing back to green on all CI services. Please note
the BSD installs will throw out some warnings during the setup phase.
They shouldn't re-occur once the images are built.
----------------------------------------------------------------
Alex Bennée (4):
.travis.yml: default the --disable-system build to --static
.travis.yml: force a brew update for MacOS builds
target/i386: fix feature check in hyperv-stub.c
migration: move port_attr inside CONFIG_LINUX
Cleber Rosa (4):
tests/vm: avoid extra compressed image copy
tests/vm: avoid image presence check and removal
tests/vm: pin ubuntu.i386 image
tests/vm: add source repos on ubuntu.i386
Gerd Hoffmann (11):
tests/vm: send proxy environment variables over ssh
tests/vm: use ssh with pty unconditionally
tests/vm: run test builds on snapshot
tests/vm: proper guest shutdown
tests/vm: add vm-boot-{ssh,serial}-<guest> targets
tests/vm: serial console support helpers
tests/vm: openbsd autoinstall, using serial console
tests/vm: freebsd autoinstall, using serial console
tests/vm: netbsd autoinstall, using serial console
tests/vm: fedora autoinstall, using serial console
tests/vm: ubuntu.i386: apt proxy setup
Philippe Mathieu-Daudé (1):
Makefile: Rename the 'vm-test' target as 'vm-help'
.travis.yml | 3 +-
Makefile | 4 +-
docs/devel/testing.rst | 4 +-
migration/rdma.c | 3 +-
target/i386/hyperv-stub.c | 2 +-
tests/vm/Makefile.include | 28 ++++++-
tests/vm/basevm.py | 135 ++++++++++++++++++++++++++++-----
tests/vm/centos | 6 +-
tests/vm/fedora | 189 ++++++++++++++++++++++++++++++++++++++++++++++
tests/vm/freebsd | 180 ++++++++++++++++++++++++++++++++++++++++---
tests/vm/netbsd | 187 ++++++++++++++++++++++++++++++++++++++++++---
tests/vm/openbsd | 159 ++++++++++++++++++++++++++++++++++----
tests/vm/ubuntu.i386 | 11 ++-
13 files changed, 842 insertions(+), 69 deletions(-)
create mode 100755 tests/vm/fedora
--
2.20.1
next reply other threads:[~2019-07-02 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 10:25 Alex Bennée [this message]
2019-07-02 23:02 ` [Qemu-devel] [PULL v2 00/20] testing/next for 4.1 Peter Maydell
2019-07-03 8:32 ` Alex Bennée
2019-07-04 7:05 ` Alex Bennée
2019-07-04 14:58 ` 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=20190702102505.32044-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--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).