From: Cleber Rosa <crosa@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org,
"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] Boot Linux Console Test: add a test for the Raspberry Pi 2
Date: Wed, 22 May 2019 17:05:44 -0400 (EDT) [thread overview]
Message-ID: <1204725743.24201394.1558559144548.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190522205234.GY10764@habkost.net>
----- Original Message -----
> From: "Eduardo Habkost" <ehabkost@redhat.com>
> To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
> Cc: qemu-devel@nongnu.org, "Cleber Rosa" <crosa@redhat.com>, "Peter Maydell" <peter.maydell@linaro.org>,
> qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>, "Andrew Baumann" <Andrew.Baumann@microsoft.com>
> Sent: Wednesday, May 22, 2019 4:52:34 PM
> Subject: Re: [Qemu-devel] [PATCH v2 2/2] Boot Linux Console Test: add a test for the Raspberry Pi 2
>
> On Wed, Mar 13, 2019 at 12:45:41AM +0100, Philippe Mathieu-Daudé wrote:
> > From: Philippe Mathieu-Daudé <f4bug@amsat.org>
> >
> > 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é <f4bug@amsat.org>
>
> 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.
>
> --
> Eduardo
>
It may be related to:
https://bugs.launchpad.net/qemu/+bug/1829779
And this is a proof that we urgently need to have a better
way of presenting/storing test artifacts. The brief output
is nice when everything goes well, but makes the test results
close to useless once a failure happens.
Philippe showed us how GitLab allows CI jobs to preserve
artifacts, so maybe the solution is to move the loads there.
- Cleber.
next prev parent reply other threads:[~2019-05-22 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190312234541.2887-1-philmd@redhat.com>
2019-05-04 11:52 ` [Qemu-devel] [PATCH v2 0/2] Acceptance Tests: Test the Raspberry Pi 2 board Philippe Mathieu-Daudé
2019-05-04 11:52 ` Philippe Mathieu-Daudé
2019-05-06 21:41 ` Eduardo Habkost
2019-05-07 5:18 ` Philippe Mathieu-Daudé
[not found] ` <20190312234541.2887-3-philmd@redhat.com>
2019-05-22 20:52 ` [Qemu-devel] [PATCH v2 2/2] Boot Linux Console Test: add a test for the Raspberry Pi 2 Eduardo Habkost
2019-05-22 21:05 ` Cleber Rosa [this message]
2019-05-23 9:29 ` Philippe Mathieu-Daudé
2019-05-23 13:40 ` Cleber Rosa
2019-06-05 20:33 ` Eduardo Habkost
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=1204725743.24201394.1558559144548.JavaMail.zimbra@redhat.com \
--to=crosa@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).