qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Liang Yan" <lyan@suse.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>, "Al Cho" <ACho@suse.com>
Subject: Re: latest GOOD state of series i386 cleanup, arm cleanup, s390 cleanup
Date: Tue, 18 May 2021 15:02:48 +0100	[thread overview]
Message-ID: <87tun0cf3d.fsf@linaro.org> (raw)
In-Reply-To: <20be5f7e-f475-4f3c-0fca-fff1750c08fe@suse.de>


Claudio Fontana <cfontana@suse.de> writes:

> On 5/17/21 11:53 AM, Claudio Fontana wrote:
>> Hello all,
>> 
>> due to my inactivity for a few weeks coupled likely with the upstream processes around qemu-6.0 now the series:
>> 
>> 1) i386 cleanup
>> 2) arm cleanup and experimental kvm-only build
>> 3) s390 cleanup
>> 
>> have become stale and hard to rebase on latest master.
>> This effect is compounded by the fact that lots of broken tests in
>> master have been added.

Which tests are these? I know master suffers a bit from occasional
falling red but to my knowledge everything should be green (at least
from my last PR anyway ;-).

>> 
>> In the interest of not losing work,
>> I provide here the latest known good state of these series:
>> 
>> For the i386 cleanup:
>> https://gitlab.com/hw-claudio/qemu/-/pipelines/293603386
>> 
>> Tests started breaking horribly since about 1/2 weeks.

The pipeline only shows one failed test (checkpatch) which is an
allowfail I believe. /me is confused.

>> The latest version of the cleanup is reachable here:
>> 
>> https://github.com/qemu/qemu.git branch "i386_cleanup_9"
>> 
>> In my understanding, Paolo has now picked up this one.
>> 
>> For the ARM cleanup and experimental kvm-only build:
>> 
>> https://gitlab.com/hw-claudio/qemu/-/pipelines/293603376
>> 
>> https://github.com/qemu/qemu.git branch "arm_cleanup_v15"
>> 
>> Again here tests started misbehaving in the same timeframe.
>> 
>> The state of ARM cleanup is still experimental, maybe Liang or Philippe you can adopt this one?
>> 
>> For the s390x cleanup:
>> 
>> https://gitlab.com/hw-claudio/qemu/-/pipelines/293603379
>> 
>> https://github.com/qemu/qemu.git branch "s390_cleanup_v1"
>> 
>> Al, can you take this one to the finish line?
>> 
>> Thanks,
>> 
>> Claudio
>> 
>
> Adding also Alex Bennee in Cc:
>
> Thanks,
>
> Claudio


-- 
Alex Bennée


  parent reply	other threads:[~2021-05-18 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  9:53 latest GOOD state of series i386 cleanup, arm cleanup, s390 cleanup Claudio Fontana
2021-05-17  9:54 ` Claudio Fontana
2021-05-17 10:11   ` Al Cho via
2021-05-18 14:02   ` Alex Bennée [this message]
2021-05-18 14:51     ` Claudio Fontana
2021-05-20 16:02       ` Alex Bennée
2021-05-24  7:30         ` Cho Yu-Chen
2021-05-24 12:06         ` Claudio Fontana

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=87tun0cf3d.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=ACho@suse.com \
    --cc=cfontana@suse.de \
    --cc=f4bug@amsat.org \
    --cc=lyan@suse.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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).