From: Eduardo Habkost <ehabkost@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Aleksandar Rikalo" <arikalo@wavecomp.com>,
qemu-devel@nongnu.org,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PULL 6/6] travis: Make check-acceptance job more verbose
Date: Wed, 12 Jun 2019 17:52:42 -0300 [thread overview]
Message-ID: <20190612205242.GQ5927@habkost.net> (raw)
In-Reply-To: <d107483c-eba8-f6fc-8e3a-ad0a86472d07@redhat.com>
On Wed, Jun 12, 2019 at 10:49:18PM +0200, Philippe Mathieu-Daudé wrote:
> On 6/11/19 7:14 PM, Eduardo Habkost wrote:
> > It will help us debug issues when tests fail.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > .travis.yml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/.travis.yml b/.travis.yml
> > index b053a836a3..a08a7b7278 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:
> >
>
> Cleber, can you help figuring what's wrong here?
>
> https://travis-ci.org/qemu/qemu/jobs/544805900
>
> The tests seems successfull, is it possible the verbose logging returns
> error to the shell even if the test succeed?
That's exactly what this patch does. On my next pull request I
will replace this with Cleber's patch that dumps the error log
only if tests failed.
--
Eduardo
next prev parent reply other threads:[~2019-06-12 20:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 17:14 [Qemu-devel] [PULL 0/6] Python queue, 2019-06-11 Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 1/6] tests/boot_linux_console: Let extract_from_deb handle various compressions Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 2/6] BootLinuxConsoleTest: Do not log empty lines Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 3/6] BootLinuxConsoleTest: Test the SmartFusion2 board Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 4/6] BootLinuxConsoleTest: Test nanoMIPS kernels on the I7200 CPU Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 5/6] BootLinuxConsoleTest: Run kerneltests BusyBox on Malta Eduardo Habkost
2019-06-11 17:14 ` [Qemu-devel] [PULL 6/6] travis: Make check-acceptance job more verbose Eduardo Habkost
2019-06-12 20:49 ` Philippe Mathieu-Daudé
2019-06-12 20:52 ` Eduardo Habkost [this message]
2019-06-12 22:33 ` Philippe Mathieu-Daudé
2019-06-12 22:47 ` Cleber Rosa
2019-06-12 23:12 ` Philippe Mathieu-Daudé
2019-06-12 12:49 ` [Qemu-devel] [PULL 0/6] Python queue, 2019-06-11 Peter Maydell
2019-06-18 13:27 ` Peter Maydell
2019-06-18 14:01 ` Cleber Rosa
2019-06-18 15:38 ` Cleber Rosa
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=20190612205242.GQ5927@habkost.net \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=crosa@redhat.com \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).