From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] shippable.yml: Remove jobs duplicated on Gitlab-CI
Date: Sun, 10 Jan 2021 12:00:08 +0100 [thread overview]
Message-ID: <e9e8be43-21e8-e483-a0f1-9370fc935bed@amsat.org> (raw)
In-Reply-To: <9c0ecc6b-0f37-2a0b-d4b9-299ba52099d3@redhat.com>
On 1/8/21 4:36 PM, Paolo Bonzini wrote:
> On 08/01/21 16:21, Daniel P. Berrangé wrote:
>> On Fri, Jan 08, 2021 at 04:14:30PM +0100, Paolo Bonzini wrote:
...
>>>
>>> The debian-mips-cross/mips-softmmu pair (and also mipsel-softmmu) is
>>> currently excluded by Gitlab's cross-mips-system, is there a reason for
>>> that? If we add it there, we can just remove shippable altogether.
Can we get this cleaned one step at a time? :)
>> Some softmmu targets were disable to keep the build time under control.
>>
>> We could enable a different subset of targets for each cross host arch,
>> so that overall we get representative coverage of the full set.
>
> Right, but at least KVM targets ought to be included in their own cross
> host.
>
> Paolo
>
next prev parent reply other threads:[~2021-01-10 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 14:51 [PATCH] shippable.yml: Remove jobs duplicated on Gitlab-CI Philippe Mathieu-Daudé
2021-01-08 15:14 ` Paolo Bonzini
2021-01-08 15:21 ` Daniel P. Berrangé
2021-01-08 15:36 ` Paolo Bonzini
2021-01-10 11:00 ` Philippe Mathieu-Daudé [this message]
2021-01-08 16:42 ` Alex Bennée
2021-01-12 9:34 ` Alex Bennée
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=e9e8be43-21e8-e483-a0f1-9370fc935bed@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.