Re: [Qemu-arm] [Qemu-devel] [PATCH v2 2/2] Boot Linux Console Test: add a test for the Raspberry Pi 2

[Eduardo Habkost]

On Thu, May 23, 2019 at 09:40:06AM -0400, Cleber Rosa wrote:
> ----- Original Message -----
> > From: "Philippe Mathieu-Daudé" <address@hidden>
> > To: "Cleber Rosa" <address@hidden>, "Eduardo Habkost" <address@hidden>
> > Cc: address@hidden, "Peter Maydell" <address@hidden>, address@hidden, 
> > "Philippe Mathieu-Daudé"
> > <address@hidden>, "Andrew Baumann" <address@hidden>, "Gerd Hoffmann" 
> > <address@hidden>
> > Sent: Thursday, May 23, 2019 5:29:22 AM
> > Subject: Re: [Qemu-devel] [PATCH v2 2/2] Boot Linux Console Test: add a 
> > test for the Raspberry Pi 2
> > 
> > On 5/22/19 11:05 PM, Cleber Rosa wrote:
> > > ----- Original Message -----
> > >> From: "Eduardo Habkost" <address@hidden>
> > >> On Wed, Mar 13, 2019 at 12:45:41AM +0100, Philippe Mathieu-Daudé wrote:
> > >>> From: Philippe Mathieu-Daudé <address@hidden>
> > >>>
> > >>> Similar to the x86_64/pc test, it boots a Linux kernel on a raspi2
> > >>> board and verify the serial is working.
> > >>>
> > >>> If ARM is a target being built, "make check-acceptance" will
> > >>> automatically include this test by the use of the "arch:arm" tags.
> > >>>
> > >>> Alternatively, this test can be run using:
> > >>>
> > >>>     $ avocado run -t arch:arm tests/acceptance
> > >>>     $ avocado run -t machine:raspi2 tests/acceptance
> > >>>
> > >>> Signed-off-by: Philippe Mathieu-Daudé <address@hidden>
> > >>
> > >> We're getting timeouts on travis-ci:
> > >> https://travis-ci.org/ehabkost/qemu/jobs/535468057#L3289
> > >>
> > >> I don't know yet if the guest is hanging, or if we just need to
> > >> increase the timeout.  I could reproduce the timeout locally,
> > >> too.
> > 
> > That's odd, I can't reproduce (this test is quicker than the following
> > test_arm_emcraft_sf2 which start u-boot then timeouts and start the kernel).
> > 
> > My guess is network issues, since this test use a different mirror:
> > archive.raspberrypi.org
> > 
> 
> It could be a network issue, it could be something else.  I think the very
> first step, and I'd urge us to get that on master ASAP, is to show the
> entire logs in CI, I mean:
> 
> ---
> 
> diff --git a/.travis.yml b/.travis.yml
> index 6fd89b3d91..fd8f6ca2d2 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -225,7 +225,7 @@ matrix:
>      # Acceptance (Functional) tests
>      - env:
>          - CONFIG="--python=/usr/bin/python3 
> --target-list=x86_64-softmmu,mips-softmmu,mips64el-softmmu,aarch64-softmmu,arm-softmmu,s390x-softmmu,alpha-softmmu"
> -        - TEST_CMD="make check-acceptance"
> +        - TEST_CMD="make AVOCADO_SHOW=test check-acceptance"
>        addons:
>          apt:
>            packages:

I have applied this change on python-next.  The failure can be
seen here:
https://travis-ci.org/ehabkost/qemu/jobs/541758418#L4033

While we don't fix this, I'm removing this test case from the
queue, so I can send a pull request.  Sorry for taking so long to
act on this.

-- 
Eduardo