On Mon, Mar 02, 2020 at 03:27:42PM +, Peter Maydell wrote:
>
> Hi -- any progress on this front? (Maybe I missed an email; if
> so, sorry about that...)
>
> thanks
> -- PMM
>
Hi Peter,
Yes, I've made some progress on some of the points raised on the last
email exchanges:
1) Jobs on
On Sat, 8 Feb 2020 at 13:08, Peter Maydell wrote:
> On Fri, 7 Feb 2020 at 20:39, Cleber Rosa wrote:
> > On Fri, Feb 07, 2020 at 04:42:10PM +, Peter Maydell wrote:
> > > This all sounds like the right thing and great progress. So yes,
> > > I agree that the next step would be to get to a
On Fri, 7 Feb 2020 at 20:39, Cleber Rosa wrote:
> On Fri, Feb 07, 2020 at 04:42:10PM +, Peter Maydell wrote:
> > This all sounds like the right thing and great progress. So yes,
> > I agree that the next step would be to get to a point where you
> > can give me some instructions on how to say
On Fri, Feb 07, 2020 at 04:42:10PM +, Peter Maydell wrote:
>
> This all sounds like the right thing and great progress. So yes,
> I agree that the next step would be to get to a point where you
> can give me some instructions on how to say "OK, here's my staging
> branch" and run it through
On Mon, 3 Feb 2020 at 03:28, Cleber Rosa wrote
>>>> Testing process:
>>>>
>>>> * I get an email which is a pull request, and I run the
>>>>"apply-pullreq" script, which takes the GIT URL and tag/branch name
>>>>to test.
>>>> * apply-pullreq performs the merge
On Sun, Feb 02, 2020 at 10:27:12PM -0500, Cleber Rosa wrote:
>>>> The set of machine I currently test on are:
>>>>
>>>> * an S390x box (this is provided to the project by IBM's Community
>>>>Cloud so can be used for the new CI setup)
>>>> * aarch32 (as a chroot on an
On Fri, Jan 17, 2020 at 02:33:54PM +, Peter Maydell wrote:
> On Mon, 2 Dec 2019 at 14:06, Cleber Rosa wrote:
> >
> > RFC: QEMU Gating CI
> > ===
> >
> > This RFC attempts to address most of the issues described in
> > "Requirements/GatinCI"[1]. An also relevant write up is
On Fri, Jan 17, 2020 at 02:33:54PM +, Peter Maydell wrote:
> On Mon, 2 Dec 2019 at 14:06, Cleber Rosa wrote:
> >
> > RFC: QEMU Gating CI
> > ===
> >
> > This RFC attempts to address most of the issues described in
> > "Requirements/GatinCI"[1]. An also relevant write up is
On Mon, 2 Dec 2019 at 14:06, Cleber Rosa wrote:
>
> RFC: QEMU Gating CI
> ===
>
> This RFC attempts to address most of the issues described in
> "Requirements/GatinCI"[1]. An also relevant write up is the "State of
> QEMU CI as we enter 4.0"[2].
>
> The general approach is one to
On Tue, Dec 03, 2019 at 02:07:32PM +, Alex Bennée wrote:
>
> Cleber Rosa writes:
>
> > RFC: QEMU Gating CI
> > ===
> >
> > This RFC attempts to address most of the issues described in
> > "Requirements/GatinCI"[1]. An also relevant write up is the "State of
> > QEMU CI as
On Tue, Dec 03, 2019 at 05:54:38PM +, Peter Maydell wrote:
> On Mon, 2 Dec 2019 at 14:06, Cleber Rosa wrote:
> >
> > RFC: QEMU Gating CI
> > ===
> >
> > This RFC attempts to address most of the issues described in
> > "Requirements/GatinCI"[1]. An also relevant write up is
On 03/12/2019 15.07, Alex Bennée wrote:
[...]
>> GitLab Jobs and Pipelines
>> -
>>
>> GitLab CI is built around two major concepts: jobs and pipelines. The
>> current GitLab CI configuration in QEMU uses jobs only (or putting it
>> another way, all jobs in a single
On Mon, 2 Dec 2019 at 14:06, Cleber Rosa wrote:
>
> RFC: QEMU Gating CI
> ===
>
> This RFC attempts to address most of the issues described in
> "Requirements/GatinCI"[1]. An also relevant write up is the "State of
> QEMU CI as we enter 4.0"[2].
>
> The general approach is one to
On Mon, Dec 02, 2019 at 01:12:54PM -0500, Cleber Rosa wrote:
> On Mon, Dec 02, 2019 at 05:00:18PM +, Stefan Hajnoczi wrote:
> > On Mon, Dec 02, 2019 at 09:05:52AM -0500, Cleber Rosa wrote:
> > > RFC: QEMU Gating CI
> > > ===
> >
> > Excellent, thank you for your work on this!
Cleber Rosa writes:
> RFC: QEMU Gating CI
> ===
>
> This RFC attempts to address most of the issues described in
> "Requirements/GatinCI"[1]. An also relevant write up is the "State of
> QEMU CI as we enter 4.0"[2].
>
> The general approach is one to minimize the
On Mon, Dec 02, 2019 at 11:36:35AM -0700, Warner Losh wrote:
>
> Just make sure that any pipeline and mandatory CI steps don't slow things
> down too much... While the examples have talked about 1 or 2 pull requests
> getting done in parallel, and that's great, the problem is when you try to
>
On Mon, Dec 2, 2019 at 11:29 AM Cleber Rosa wrote:
> On Mon, Dec 02, 2019 at 05:08:35PM +, Peter Maydell wrote:
> > On Mon, 2 Dec 2019 at 17:00, Stefan Hajnoczi
> wrote:
> > >
> > > On Mon, Dec 02, 2019 at 09:05:52AM -0500, Cleber Rosa wrote:
> > > > To exemplify my point, if one specific
On Mon, Dec 02, 2019 at 05:08:35PM +, Peter Maydell wrote:
> On Mon, 2 Dec 2019 at 17:00, Stefan Hajnoczi wrote:
> >
> > On Mon, Dec 02, 2019 at 09:05:52AM -0500, Cleber Rosa wrote:
> > > To exemplify my point, if one specific test run as part of "check-tcg"
> > > is found to be faulty on a
On Mon, Dec 02, 2019 at 05:00:18PM +, Stefan Hajnoczi wrote:
> On Mon, Dec 02, 2019 at 09:05:52AM -0500, Cleber Rosa wrote:
> > RFC: QEMU Gating CI
> > ===
>
> Excellent, thank you for your work on this!
>
> >
> > This RFC attempts to address most of the issues described in
On Mon, 2 Dec 2019 at 17:00, Stefan Hajnoczi wrote:
>
> On Mon, Dec 02, 2019 at 09:05:52AM -0500, Cleber Rosa wrote:
> > To exemplify my point, if one specific test run as part of "check-tcg"
> > is found to be faulty on a specific job (say on a specific OS), the
> > entire "check-tcg" test set
On Mon, Dec 02, 2019 at 09:05:52AM -0500, Cleber Rosa wrote:
> RFC: QEMU Gating CI
> ===
Excellent, thank you for your work on this!
>
> This RFC attempts to address most of the issues described in
> "Requirements/GatinCI"[1]. An also relevant write up is the "State of
> QEMU
21 matches
Mail list logo
