qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 0/2] hw/arm/raspi: Remove deprecated raspi2/raspi3 aliases


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH v2 0/2] hw/arm/raspi: Remove deprecated raspi2/raspi3 aliases
Date: Wed, 15 Sep 2021 09:37:56 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

On 9/15/21 2:34 AM, John Snow wrote:
> On Fri, Aug 27, 2021 at 2:30 PM Philippe Mathieu-Daudé <f4bug@amsat.org
> <mailto:f4bug@amsat.org>> wrote:
> 
>     On 8/27/21 8:01 PM, Willian Rampazzo wrote:
>     > Hi, Phil,
>     >
>     > On Thu, Aug 26, 2021 at 1:49 PM Philippe Mathieu-Daudé
>     <f4bug@amsat.org <mailto:f4bug@amsat.org>> wrote:
>     >>
>     >> Hi Peter,
>     >>
>     >> On 7/9/21 6:00 PM, Peter Maydell wrote:
>     >>> On Fri, 9 Jul 2021 at 16:33, Peter Maydell
>     <peter.maydell@linaro.org <mailto:peter.maydell@linaro.org>> wrote:
>     >>>>
>     >>>> On Thu, 8 Jul 2021 at 15:55, Philippe Mathieu-Daudé
>     <f4bug@amsat.org <mailto:f4bug@amsat.org>> wrote:
>     >>>>>
>     >>>>> Since v1:
>     >>>>> - renamed tests (Peter)
>     >>>>>
>     >>>>> Philippe Mathieu-Daudé (2):
>     >>>>>   tests: Remove uses of deprecated raspi2/raspi3 machine names
>     >>>>>   hw/arm/raspi: Remove deprecated raspi2/raspi3 aliases
>     >>>>
>     >>>>
>     >>>>
>     >>>> Applied to target-arm.next, thanks.
>     >>>
>     >>> I found that this seems to break 'make check':
>     >>>
>     >>>  (09/52)
>     
> tests/acceptance/boot_linux_console.py:BootLinuxConsole.test_arm_raspi2_initrd:
>     >>> ERROR: Could not perform graceful shutdown (40.38 s)
>     >>
>     >> I can not reproduce. Maybe something got changed in Python/Avocado
>     >> since... I'm going to simply respin (updating 6.1 -> 6.2).
>     >
>     > I also could not reproduce. I checked and nothing changed on the
>     > Avocado side. The version is still the same on the QEMU side.
> 
>     Thanks for double-checking!
> 
> 
> Sorry for the long silence.
> 
> Did you get this sorted out? I don't recall changing the QEMUMachine
> code upstream lately (Though I have been tinkering with it a lot in my
> own branches) -- was the root cause of the failure discovered?

No. Peter tested again and it passed, then this eventually got merged.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]