From: Cleber Rosa <crosa@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Max Reitz" <mreitz@redhat.com>,
qemu-block@nongnu.org, "Fam Zheng" <fam@euphon.net>
Subject: Re: [Qemu-devel] [PATCH 0/2] qemu-iotests: add a Travis job
Date: Mon, 18 Feb 2019 13:05:41 -0500 [thread overview]
Message-ID: <35c3b6d2-01fb-dd01-0c10-7de15e774499@redhat.com> (raw)
In-Reply-To: <20190209040132.25573-1-crosa@redhat.com>
On 2/8/19 11:01 PM, Cleber Rosa wrote:
> Besides the obvious reasons of testing more, and somewhat for free,
> running the qemu-iotests along the other tests on Travis also makes
> sure that changes to shared code such as "scripts/qemu.py" and the
> like won't break other users of the same code.
>
> Cleber Rosa (2):
> qemu-iotests: only enable kvm if the host seems to support it
> qemu-iotests: add "make check-block" job to Travis
>
> .travis.yml | 8 ++++++++
> tests/qemu-iotests/235 | 5 +++--
> tests/qemu-iotests/238 | 5 +++--
> 3 files changed, 14 insertions(+), 4 deletions(-)
>
Just a follow up showing the results for the added Travis job:
https://travis-ci.org/clebergnu/qemu/jobs/490806941#L2321
Cheers,
- Cleber.
prev parent reply other threads:[~2019-02-18 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 4:01 [Qemu-devel] [PATCH 0/2] qemu-iotests: add a Travis job Cleber Rosa
2019-02-09 4:01 ` [Qemu-devel] [PATCH 1/2] qemu-iotests: only enable kvm if the host seems to support it Cleber Rosa
2019-02-09 4:01 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: add "make check-block" job to Travis Cleber Rosa
2019-02-18 18:05 ` Cleber Rosa [this message]
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=35c3b6d2-01fb-dd01-0c10-7de15e774499@redhat.com \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@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 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).