From: Arnaldo Carvalho de Melo <acme@redhat.com>

Hi,

	While evaluating what is needed for having shell tests that test
python functionality conditionally, i.e. so that we don't try to test
the python binding if NO_LIBPYTHON=1 is used, I stumbled into these
problems.

	The first patch its more for documenting that strange system()
behaviour and to check if this was something that would have
implications in other 'perf test' cases besides this python one, maybe
somebody will spot the problem, but at least it seems more compact now
using 'python -c inline-python-source'.

- Arnaldo

Arnaldo Carvalho de Melo (2):
  perf test python: Robustify the 'perf test python' test case
  perf test: Don't build the python binding builtin test case with NO_LIBPYTHON=1

 tools/perf/tests/Build          | 2 +-
 tools/perf/tests/builtin-test.c | 2 ++
 tools/perf/tests/python-use.c   | 4 ++--
 tools/perf/tests/tests.h        | 2 ++
 4 files changed, 7 insertions(+), 3 deletions(-)

-- 
2.47.0