[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: no more pullreq processing til February
From: |
Peter Maydell |
Subject: |
Re: no more pullreq processing til February |
Date: |
Thu, 26 Jan 2023 14:41:03 +0000 |
On Thu, 26 Jan 2023 at 14:35, Daniel P. Berrangé <berrange@redhat.com> wrote:
> I'm confident we can rationalize our jobs, especially the cross
> compilation ones.
>
> For each non-x86 arch we've got two sets of jobs, one for system
> emulators and one for user emulators.
>
> IMHO the most interesting part of non-x86 testing is the TCG
> host target. We don't need 2 jobs to cover that, either system
> or user emulators would cover TCG build / test. Most of the rest
> of code is not heavily host arch dependant.
I'm not super enthusiastic about cutting this down.
I find the non-x86 testing is the most interesting part
of the CI -- most patch submitters and system submaintainers
have already done local compile-and-build with the common
x86_64 recent-distro target, so those parts pretty much
always succeed. The benefit of the auto CI is in keeping
the platforms that aren't so widely used by developers
working (both different-host-arch and different-OS).
thanks
-- PMM
- Re: no more pullreq processing til February, (continued)
Re: no more pullreq processing til February, Daniel P . Berrangé, 2023/01/26
Re: no more pullreq processing til February, Alex Bennée, 2023/01/26
Re: no more pullreq processing til February, Stefan Hajnoczi, 2023/01/26
- Re: no more pullreq processing til February, Peter Maydell, 2023/01/26
- Re: no more pullreq processing til February, Thomas Huth, 2023/01/27
- Re: no more pullreq processing til February, Kevin Wolf, 2023/01/27
- Re: no more pullreq processing til February, Daniel P . Berrangé, 2023/01/27
- Re: no more pullreq processing til February, Peter Maydell, 2023/01/27
- Re: no more pullreq processing til February, Peter Maydell, 2023/01/27
Re: no more pullreq processing til February, Markus Armbruster, 2023/01/27