From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Samuel Ortiz" <sameo@linux.intel.com>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] more automated/public CI for QEMU pullreqs
Date: Thu, 22 Aug 2019 13:14:25 +0200 [thread overview]
Message-ID: <18cdf90d-1724-e7bf-2079-b7ec829256f0@redhat.com> (raw)
In-Reply-To: <CAFEAcA8c_BukhU+ZgfqUxPUqsOaN6MJdJL5n3-Daf-j05ZeTig@mail.gmail.com>
On 22/08/19 13:04, Peter Maydell wrote:
> On Thu, 22 Aug 2019 at 11:50, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>> One-off tasks:
>>
>> 1. Create CI runners that offer similar cross-architecture coverage to
>> Peter's current setup. qemu.org has some x86, ppc, and s390 server
>> resources available. I'm not sure about ARM and other architectures.
>
> Quick list of what I currently have:
> * freebsd/openbsd/netbsd -- these are just running the tests/vm stuff
> * an x86-64 machine doing the w32/w64 crossbuilds
> * aarch64
> * aarch32 (done via chroot on an aarch64 box)
> * osx
I was thinking of setting up a Macincloud account with a Patchew runner
for this.
> * ppc64 (on a gcc compile farm machine)
> * s390 (on a machine Christian arranged for project use)
Great, we could also move the Patchew tester off the Fedora machine that
is getting a bit crowded.
David, any chance you could add Docker support to ppc64 builds? I don't
feel too comfortable doing untrusted builds inside the RH network
without any protection from containers etc.
> Of those the s390 is OK for project use. I'm not sure the gcc
> compile farm stuff is recommended for fully automatic CI, so
> if we can avoid that it would be better. Linaro can probably
> provide some arm-server resources but I haven't checked/asked yet.
Same as above for Docker support. If ARM builds can be containerized, I
can also look for resources inside Red Hat.
Paolo
next prev parent reply other threads:[~2019-08-22 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 18:16 [Qemu-devel] more automated/public CI for QEMU pullreqs Peter Maydell
2019-08-22 10:49 ` Stefan Hajnoczi
2019-08-22 11:04 ` Peter Maydell
2019-08-22 11:14 ` Paolo Bonzini [this message]
2019-09-30 12:53 ` Peter Maydell
2019-10-04 9:31 ` Stefan Hajnoczi
2019-08-22 11:47 ` [Qemu-devel] " Daniel P. Berrangé
2019-08-22 16:31 ` Dr. David Alan Gilbert
2019-08-22 16:48 ` Paolo Bonzini
2019-08-22 16:50 ` Dr. David Alan Gilbert
2019-08-22 17:05 ` Paolo Bonzini
2019-08-23 13:15 ` Philippe Mathieu-Daudé
2019-08-24 7:44 ` Alex Bennée
2019-08-22 17:03 ` Daniel P. Berrangé
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=18cdf90d-1724-e7bf-2079-b7ec829256f0@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=kchamart@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sameo@linux.intel.com \
--cc=stefanha@redhat.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).