From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Thomas Richter <tmricht@linux.vnet.ibm.com>,
Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: fix perf test case 14 result reporting
Date: Thu, 1 Jun 2017 23:04:51 +0200 [thread overview]
Message-ID: <20170601210451.GA5713@krava> (raw)
In-Reply-To: <20170601132038.GG2899@kernel.org>
On Thu, Jun 01, 2017 at 10:20:38AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 01, 2017 at 02:34:41PM +0200, Thomas Richter escreveu:
> > Command perf test -v 14 (Setup struct perf_event_attr test)
> > always reports success even if the test case fails.
> > It works correctly if you also specify -F (for don't fork).
>
> Thanks for working on this, adding Jiri Olsa, that wrote this test
> harness, so that he can check and provide his Acked-by or Reviewed-by,
> Jiri?
>
> - Arnaldo
>
> > root@s35lp76 perf]# ./perf test -v 14
> > 14: Setup struct perf_event_attr :
> > --- start ---
> > running './tests/attr/test-record-no-delay'
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.002 MB /tmp/tmp4E1h7R/perf.data
> > (1 samples) ]
> > expected task=0, got 1
> > expected precise_ip=0, got 3
> > expected wakeup_events=1, got 0
> > FAILED './tests/attr/test-record-no-delay' - match failure
> > test child finished with 0
> > ---- end ----
> > Setup struct perf_event_attr: Ok
> >
> > The reason for the wrong error reporting is the return value of the
> > system() library call. It is called in run_dir() file tests/attr.c
> > and returns the exit status, in above case 0xff00.
> > This value is given as parameter to the exit() function which
> > can only handle values 0-0xff.
> > The child process terminates with exit value of 0 and the parent
> > does not detect any error.
> >
> > This patch corrects the error reporting and prints the
> > correct test result.
> >
> > Signed-off-by: Thomas Richter <tmricht@linux.vnet.ibm.com>
> > Reviewed-by: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
> > ---
> > tools/perf/tests/attr.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
> > index 88dc51f..131b510 100644
> > --- a/tools/perf/tests/attr.c
> > +++ b/tools/perf/tests/attr.c
> > @@ -150,7 +150,7 @@ static int run_dir(const char *d, const char *perf)
> > snprintf(cmd, 3*PATH_MAX, PYTHON " %s/attr.py -d %s/attr/ -p %s %.*s",
> > d, d, perf, vcnt, v);
> >
> > - return system(cmd);
> > + return system(cmd) ? TEST_FAIL : TEST_OK;
> > }
> >
> > int test__attr(int subtest __maybe_unused)
> > --
> > 2.9.3
seems ok, however "perf test attr" is broken ATM, since it wasn't updated
for some time as it showed false 'Ok'
I started fixing it some time ago, but got distracted, if you are
interested, you're welcome to pick up from my branch ;-)
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/attr_test
thanks,
jirka
next prev parent reply other threads:[~2017-06-01 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 12:34 [PATCH] perf: fix perf test case 14 result reporting Thomas Richter
2017-06-01 13:20 ` Arnaldo Carvalho de Melo
2017-06-01 21:04 ` Jiri Olsa [this message]
2017-06-02 9:58 ` Thomas-Mich Richter
2017-06-02 14:09 ` Arnaldo Carvalho de Melo
2017-06-02 14:11 ` Arnaldo Carvalho de Melo
2017-06-04 18:51 ` Jiri Olsa
2017-06-06 5:02 ` Thomas-Mich Richter
2017-06-04 18:51 ` Jiri Olsa
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=20170601210451.GA5713@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmricht@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).