From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, frankja@linux.vnet.ibm.com,
david@redhat.com, pmorel@linux.ibm.com,
linux-s390@vger.kernel.org, imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests GIT PULL 00/11] s390x patches
Date: Fri, 31 Jul 2020 14:09:32 +0200 [thread overview]
Message-ID: <00cc99d2-6020-3111-38a4-232991ffcf0d@redhat.com> (raw)
In-Reply-To: <524d5b00-94ec-da47-601a-a5909e3ed63e@linux.ibm.com>
On 31/07/2020 13.31, Janosch Frank wrote:
> On 7/31/20 12:31 PM, Paolo Bonzini wrote:
>> On 31/07/20 11:45, Janosch Frank wrote:
>>> https://github.com/frankjaa/kvm-unit-tests.git tags/s390x-2020-31-07
>>
>> Pulled, thanks. FWIW you may want to gitlab in order to get the CI.
>>
>> Paolo
>>
>
> Hey Paolo, that repository is hooked up to travis already:
> https://travis-ci.com/github/frankjaa/kvm-unit-tests/builds/177931162
>
> I'll consider it if it has any benefit.
> @Thomas: Are there differences in the CI?
Not that much, you get a good build test coverage with both. Travis uses
real (nested) KVM tests, but the compiler and QEMU versions are a little
bit backlevel (still using Ubuntu bionic). Gitlab-CI uses newer versions
(thanks to Fedora 32), but there is no KVM support here, so the tests
run with TCG only (I'm thinking of adding the cirrus-run script to the
Gitlab-CI, maybe we could get some KVM-coverage that way there, too, but
that will certainly take some time to figure it out).
Thomas
next prev parent reply other threads:[~2020-07-31 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 9:45 [kvm-unit-tests GIT PULL 00/11] s390x patches Janosch Frank
2020-07-31 9:45 ` [kvm-unit-tests GIT PULL 01/11] s390x/cpumodel: The missing DFP facility on TCG is expected Janosch Frank
2020-07-31 9:45 ` [kvm-unit-tests GIT PULL 02/11] s390x: saving regs for interrupts Janosch Frank
2020-07-31 9:45 ` [kvm-unit-tests GIT PULL 03/11] s390x: I/O interrupt registration Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 04/11] s390x: export the clock get_clock_ms() utility Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 05/11] s390x: clock and delays calculations Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 06/11] s390x: define function to wait for interrupt Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 07/11] s390x: Library resources for CSS tests Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 08/11] s390x: css: stsch, enumeration test Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 09/11] s390x: css: msch, enable test Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 10/11] s390x: css: ssch/tsch with sense and interrupt Janosch Frank
2020-07-31 9:46 ` [kvm-unit-tests GIT PULL 11/11] s390x: fix inline asm on gcc10 Janosch Frank
2020-07-31 10:31 ` [kvm-unit-tests GIT PULL 00/11] s390x patches Paolo Bonzini
2020-07-31 11:31 ` Janosch Frank
2020-07-31 12:09 ` Thomas Huth [this message]
2020-07-31 12:31 ` Janosch Frank
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=00cc99d2-6020-3111-38a4-232991ffcf0d@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.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).