From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: Make check-parallel return non-zero if a test failed
Date: Tue, 19 Jan 2016 11:15:00 -0000 [thread overview]
Message-ID: <569E1ADD.9010808@redhat.com> (raw)
In-Reply-To: <1453157331-5472-1-git-send-email-simon.marchi@ericsson.com>
On 01/18/2016 10:48 PM, Simon Marchi wrote:
> When using the check-parallel target, the return code of make is always 0,
> regardless of test results. This patch makes it return the same code as
> the "make do-check-parallel" sub-command. So if there is a FAIL somewhere,
> non-zero will be returned by make.
>
> For the sake of example, I introduced a failure in gdb.base/break.exp.
>
> $ make check-single TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
> ...
> FAIL: gdb.base/break.exp: allo
> ...
> Fail :(
>
> I think the parallel run should do the same. Currently:
>
> $ make check-parallel TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
> ...
> FAIL: gdb.base/break.exp: allo
> ...
> Success :D
>
> And with the patch (no big surprises there):
>
> $ make check-parallel TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
> ...
> FAIL: gdb.base/break.exp: allo
> ...
> Fail :(
>
> What do you think?
This has occasionally annoyed me too. Thanks for fixing this!
LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-19 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 22:49 Simon Marchi
2016-01-19 11:15 ` Pedro Alves [this message]
2016-01-19 15:51 ` Simon Marchi
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=569E1ADD.9010808@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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