From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
David Ahern <dsahern@gmail.com>, Don Zickus <dzickus@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL 0/2] perf/tests improvements
Date: Fri, 6 Jun 2014 11:11:47 -0300 [thread overview]
Message-ID: <1402063909-13859-1-git-send-email-acme@kernel.org> (raw)
Hi Jiri,
Experimenting with more topic branches, this time for things you're the
are the original developer and de facto maintainer, the tools/perf/tests/ harness.
This was done on top of your perf/core branch, please let me know if all is
ok and then you can try pulling from it or perhaps you could just ack it and then
Ingo could pull it directly, opinions? Ingo?
- Arnaldo
The following changes since commit 1bb7b24b0457eeea549262780c0b9d0755416e2f:
perf tools: Support spark lines in perf stat (2014-06-06 11:54:06 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tests-for-jirka
for you to fetch changes up to 38b8d135293e110780eaa02b021eb9c13c4009a6:
perf tests: Show the inner make output when an error happens (2014-06-06 10:45:09 -0300)
----------------------------------------------------------------
perf/tests improvements:
Developer stuff.
. Emit more precise message for missing glibc static library,
from Arnaldo Carvalho de Melo.
. Show the 'make -f tests/make' inner make output when an error happens.
The perf build tests harness, invoked with:
make -C tools/perf -f tests/make
Will call many combinations of builds, trying to check if all of them
continue to work over time, for instance, if removing perl support, or
if building using static libraries still builds fine.
But one would have to check the contents of a per build test entry
file to figure out what the error was about. Do it automatically,
speeding up the process of, for instance, installing missing static
libraries.
from Arnaldo Carvalho de Melo.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
----------------------------------------------------------------
Arnaldo Carvalho de Melo (2):
perf tools: Emit more precise message for missing glibc static library
perf tests: Show the inner make output when an error happens
tools/perf/config/Makefile | 6 +++++-
tools/perf/tests/make | 3 +--
2 files changed, 6 insertions(+), 3 deletions(-)
next reply other threads:[~2014-06-06 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 14:11 Arnaldo Carvalho de Melo [this message]
2014-06-06 14:11 ` [PATCH 1/2] perf tools: Emit more precise message for missing glibc static library Arnaldo Carvalho de Melo
2014-06-10 15:50 ` Don Zickus
2014-06-10 18:16 ` perf tools: MULTILIB install issues. was " Arnaldo Carvalho de Melo
2014-06-06 14:11 ` [PATCH 2/2] perf tests: Show the inner make output when an error happens Arnaldo Carvalho de Melo
2014-06-06 14:50 ` Jiri Olsa
2014-06-06 15:45 ` Arnaldo Carvalho de Melo
2014-06-06 14:51 ` [GIT PULL 0/2] perf/tests improvements Jiri Olsa
2014-06-06 15:06 ` Arnaldo Carvalho de Melo
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=1402063909-13859-1-git-send-email-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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