From: Andi Kleen <ak@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
peterz@infradead.org, acme@kernel.org, eranian@google.com,
jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] perf, tools: Add test cases for new data source encoding
Date: Mon, 5 Jun 2017 15:49:55 -0700 [thread overview]
Message-ID: <20170605224955.GA30867@tassilo.jf.intel.com> (raw)
In-Reply-To: <20170605103317.GA28871@krava>
> [jolsa@krava perf]$ ./perf test source -v
> 5: Test data source output :
> --- start ---
> test child forked, pid 8689
> FAILED tests/mem.c:20 unexpected FwdRAM miss
> test child finished with -1
> ---- end ----
> Test data source output: FAILED!
Ah, was a last minute edit that broke it. I posted a v2 that fixes the test.
Thanks.
-Andi
next prev parent reply other threads:[~2017-06-05 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 20:12 [PATCH 1/6] perf/x86: Move Nehalem PEBS code to flag Andi Kleen
2017-06-02 20:12 ` [PATCH 2/6] perf/x86: Fix data source decoding for Skylake Andi Kleen
2017-06-02 20:12 ` [PATCH 3/6] perf, tools: Add support for printing new mem_info encodings Andi Kleen
2017-06-02 20:12 ` [PATCH 4/6] perf/x86: Add support for PEBS sampling persistent RAM on Skylake Andi Kleen
2017-06-02 20:12 ` [PATCH 5/6] perf, tools: Support persistent memory encoding Andi Kleen
2017-06-02 20:12 ` [PATCH 6/6] perf, tools: Add test cases for new data source encoding Andi Kleen
2017-06-05 10:33 ` Jiri Olsa
2017-06-05 22:49 ` Andi Kleen [this message]
2017-06-07 2:08 ` [lkp-robot] [perf, tools] d03bd7bd14: perf-sanity-tests.Test_data_source_output.fail kernel test robot
2017-06-05 22:48 [PATCH 1/6] perf/x86: Move Nehalem PEBS code to flag Andi Kleen
2017-06-05 22:48 ` [PATCH 6/6] perf, tools: Add test cases for new data source encoding Andi Kleen
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=20170605224955.GA30867@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
Powered by JetHome