[PATCH 0/9] perf test: the testsuite again

[PATCH 0/9] perf test: the testsuite again

[Michael Petlan]

Hi all,

after some time, I am sending the proposed testsuite again. I have fixed
couple of things there since last time.

   * three verbosity levels are now supported (perf test suite -vv)
   * logs and temp files are stored in /tmp/, so the main tree is not
     spoiled anymore
   * more things can be parametrized from the outside
   * log parsing should be more robust now

The testsuite is roughly tested on x86_64, i386, ppc64, s390x and aarch64.
The following patches should be applicable upon the Arnaldo's tree, to the
'perf/core' branch.

Some issues to be discussed:

1) Packaging

While the other tests are packed within perf, the character of this suite
does not fit that model very well. Nowadays, it is run only when the dir
'testsuite' is found in the current dir. Otherwise the test is skipped.
I still haven't found any better solution for this.

2) In case it gets into the kernel tree, where the 'upstream' will be?

I have been developing the suite in my github repository [1]. I am planning
to continue with that, if the suite gets or not into the kernel tree. There
are still many testcases missing. I also backport the suite for RHEL testing
purposes.

It is easier for me to continue the development there and merge bigger
chunks into the kernel tree, than move all the development here. Is that
an acceptable model?

Is there anything else that you would like to point at?

Thanks.
Michael



[1] https://github.com/rfmvh/perftool-testsuite

Michael Petlan (9):
   perf test: Adding an entry for the perftool-testsuite
   perf test: adding new testsuite: common files
   perf test: new testsuite: perf annotate tests
   perf test: new testsuite: perf buildid-list tests
   perf test: new testsuite: perf list tests
   perf test: new testsuite: perf probe tests
   perf test: new testsuite: perf report tests
   perf test: new testsuite: perf stat tests
   perf test: new testsuite: perf trace tests

  tools/perf/tests/Build                             |   1 +
  tools/perf/tests/builtin-test.c                    |   4 +
  tools/perf/tests/suite.c                           | 150 ++++++++++++++
  tools/perf/tests/suite.h                           |  30 +++
  tools/perf/tests/tests.h                           |   1 +
  tools/perf/testsuite/base_annotate/cleanup.sh      |  24 +++
  .../perf/testsuite/base_annotate/examples/Makefile |  16 ++
  tools/perf/testsuite/base_annotate/examples/load.c |  24 +++
  tools/perf/testsuite/base_annotate/settings.sh     |  31 +++
  tools/perf/testsuite/base_annotate/setup.sh        |  35 ++++
  tools/perf/testsuite/base_annotate/test_basic.sh   | 169 +++++++++++++++
  tools/perf/testsuite/base_buildid/cleanup.sh       |  23 +++
  tools/perf/testsuite/base_buildid/settings.sh      |  45 ++++
  tools/perf/testsuite/base_buildid/setup.sh         |  26 +++
  .../testsuite/base_buildid/test_buildid-list.sh    |  81 ++++++++
  tools/perf/testsuite/base_list/cleanup.sh          |  22 ++
  tools/perf/testsuite/base_list/settings.sh         |  30 +++
  tools/perf/testsuite/base_list/setup.sh            |  20 ++
  tools/perf/testsuite/base_list/test_basic.sh       | 101 +++++++++
  tools/perf/testsuite/base_probe/cleanup.sh         |  22 ++
  tools/perf/testsuite/base_probe/examples/Makefile  |  16 ++
  .../perf/testsuite/base_probe/examples/advanced.c  |  40 ++++
  .../testsuite/base_probe/examples/exact_counts.c   |  35 ++++
  tools/perf/testsuite/base_probe/examples/test.c    |  35 ++++
  tools/perf/testsuite/base_probe/settings.sh        |  58 ++++++
  tools/perf/testsuite/base_probe/setup.sh           |  23 +++
  .../base_probe/test_adding_blacklisted.sh          |  63 ++++++
  .../testsuite/base_probe/test_adding_kernel.sh     | 229 +++++++++++++++++++++
  tools/perf/testsuite/base_probe/test_advanced.sh   | 124 +++++++++++
  tools/perf/testsuite/base_probe/test_basic.sh      |  79 +++++++
  .../perf/testsuite/base_probe/test_exact_counts.sh | 106 ++++++++++
  .../testsuite/base_probe/test_invalid_options.sh   |  80 +++++++
  .../testsuite/base_probe/test_line_semantics.sh    |  56 +++++
  tools/perf/testsuite/base_probe/test_listing.sh    | 154 ++++++++++++++
  .../perf/testsuite/base_probe/test_probe_syntax.sh | 119 +++++++++++
  tools/perf/testsuite/base_report/cleanup.sh        |  24 +++
  tools/perf/testsuite/base_report/settings.sh       |  30 +++
  tools/perf/testsuite/base_report/setup.sh          |  26 +++
  .../testsuite/base_report/stderr-whitelist.txt     |   1 +
  tools/perf/testsuite/base_report/test_basic.sh     | 169 +++++++++++++++
  tools/perf/testsuite/base_stat/cleanup.sh          |  26 +++
  tools/perf/testsuite/base_stat/settings.sh         |  25 +++
  tools/perf/testsuite/base_stat/test_basic.sh       |  69 +++++++
  tools/perf/testsuite/base_stat/test_hw.sh          |  50 +++++
  tools/perf/testsuite/base_stat/test_hwcache.sh     |  51 +++++
  .../perf/testsuite/base_stat/test_intel_uncore.sh  |  46 +++++
  .../testsuite/base_stat/test_powerpc_hv_24x7.sh    |  60 ++++++
  .../base_stat/test_tracepoints_definition.sh       |  62 ++++++
  tools/perf/testsuite/base_trace/cleanup.sh         |  24 +++
  tools/perf/testsuite/base_trace/settings.sh        |  25 +++
  tools/perf/testsuite/base_trace/setup.sh           |  16 ++
  .../perf/testsuite/base_trace/stderr-whitelist.txt |   1 +
  tools/perf/testsuite/base_trace/test_basic.sh      | 131 ++++++++++++
  tools/perf/testsuite/base_trace/test_overhead.sh   |  51 +++++
  tools/perf/testsuite/base_trace/test_record.sh     |  45 ++++
  .../testsuite/common/check_all_lines_matched.pl    |  38 ++++
  .../testsuite/common/check_all_patterns_found.pl   |  33 +++
  .../testsuite/common/check_any_pattern_found.pl    |  14 ++
  .../testsuite/common/check_buildids_vs_files.pl    |  31 +++
  .../testsuite/common/check_errors_whitelisted.pl   |  50 +++++
  .../testsuite/common/check_exact_pattern_order.pl  |  27 +++
  .../testsuite/common/check_kallsyms_vs_probes.pl   |  61 ++++++
  .../testsuite/common/check_no_patterns_found.pl    |  33 +++
  tools/perf/testsuite/common/init.sh                |  67 ++++++
  tools/perf/testsuite/common/parametrization.sh     |  39 ++++
  tools/perf/testsuite/common/patterns.sh            | 119 +++++++++++
  tools/perf/testsuite/common/settings.sh            |  57 +++++
  67 files changed, 3573 insertions(+)
  create mode 100644 tools/perf/tests/suite.c
  create mode 100644 tools/perf/tests/suite.h
  create mode 100755 tools/perf/testsuite/base_annotate/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_annotate/examples/Makefile
  create mode 100644 tools/perf/testsuite/base_annotate/examples/load.c
  create mode 100644 tools/perf/testsuite/base_annotate/settings.sh
  create mode 100755 tools/perf/testsuite/base_annotate/setup.sh
  create mode 100755 tools/perf/testsuite/base_annotate/test_basic.sh
  create mode 100755 tools/perf/testsuite/base_buildid/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_buildid/settings.sh
  create mode 100755 tools/perf/testsuite/base_buildid/setup.sh
  create mode 100755 tools/perf/testsuite/base_buildid/test_buildid-list.sh
  create mode 100755 tools/perf/testsuite/base_list/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_list/settings.sh
  create mode 100755 tools/perf/testsuite/base_list/setup.sh
  create mode 100755 tools/perf/testsuite/base_list/test_basic.sh
  create mode 100755 tools/perf/testsuite/base_probe/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_probe/examples/Makefile
  create mode 100644 tools/perf/testsuite/base_probe/examples/advanced.c
  create mode 100644 tools/perf/testsuite/base_probe/examples/exact_counts.c
  create mode 100644 tools/perf/testsuite/base_probe/examples/test.c
  create mode 100644 tools/perf/testsuite/base_probe/settings.sh
  create mode 100755 tools/perf/testsuite/base_probe/setup.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_adding_blacklisted.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_adding_kernel.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_advanced.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_basic.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_exact_counts.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_invalid_options.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_line_semantics.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_listing.sh
  create mode 100755 tools/perf/testsuite/base_probe/test_probe_syntax.sh
  create mode 100755 tools/perf/testsuite/base_report/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_report/settings.sh
  create mode 100755 tools/perf/testsuite/base_report/setup.sh
  create mode 100644 tools/perf/testsuite/base_report/stderr-whitelist.txt
  create mode 100755 tools/perf/testsuite/base_report/test_basic.sh
  create mode 100755 tools/perf/testsuite/base_stat/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_stat/settings.sh
  create mode 100755 tools/perf/testsuite/base_stat/test_basic.sh
  create mode 100755 tools/perf/testsuite/base_stat/test_hw.sh
  create mode 100755 tools/perf/testsuite/base_stat/test_hwcache.sh
  create mode 100755 tools/perf/testsuite/base_stat/test_intel_uncore.sh
  create mode 100755 tools/perf/testsuite/base_stat/test_powerpc_hv_24x7.sh
  create mode 100755 tools/perf/testsuite/base_stat/test_tracepoints_definition.sh
  create mode 100755 tools/perf/testsuite/base_trace/cleanup.sh
  create mode 100644 tools/perf/testsuite/base_trace/settings.sh
  create mode 100755 tools/perf/testsuite/base_trace/setup.sh
  create mode 100644 tools/perf/testsuite/base_trace/stderr-whitelist.txt
  create mode 100755 tools/perf/testsuite/base_trace/test_basic.sh
  create mode 100755 tools/perf/testsuite/base_trace/test_overhead.sh
  create mode 100755 tools/perf/testsuite/base_trace/test_record.sh
  create mode 100755 tools/perf/testsuite/common/check_all_lines_matched.pl
  create mode 100755 tools/perf/testsuite/common/check_all_patterns_found.pl
  create mode 100755 tools/perf/testsuite/common/check_any_pattern_found.pl
  create mode 100755 tools/perf/testsuite/common/check_buildids_vs_files.pl
  create mode 100755 tools/perf/testsuite/common/check_errors_whitelisted.pl
  create mode 100755 tools/perf/testsuite/common/check_exact_pattern_order.pl
  create mode 100755 tools/perf/testsuite/common/check_kallsyms_vs_probes.pl
  create mode 100755 tools/perf/testsuite/common/check_no_patterns_found.pl
  create mode 100644 tools/perf/testsuite/common/init.sh
  create mode 100644 tools/perf/testsuite/common/parametrization.sh
  create mode 100644 tools/perf/testsuite/common/patterns.sh
  create mode 100644 tools/perf/testsuite/common/settings.sh

-- 
1.8.3.1

Re: [PATCH 0/9] perf test: the testsuite again

[Jiri Olsa]

On Wed, Mar 16, 2016 at 02:50:06PM +0100, Michael Petlan wrote:
> Hi all,
> 
> after some time, I am sending the proposed testsuite again. I have fixed
> couple of things there since last time.
> 
>   * three verbosity levels are now supported (perf test suite -vv)
>   * logs and temp files are stored in /tmp/, so the main tree is not
>     spoiled anymore
>   * more things can be parametrized from the outside
>   * log parsing should be more robust now
> 
> The testsuite is roughly tested on x86_64, i386, ppc64, s390x and aarch64.
> The following patches should be applicable upon the Arnaldo's tree, to the
> 'perf/core' branch.
> 
> Some issues to be discussed:
> 
> 1) Packaging
> 
> While the other tests are packed within perf, the character of this suite
> does not fit that model very well. Nowadays, it is run only when the dir
> 'testsuite' is found in the current dir. Otherwise the test is skipped.
> I still haven't found any better solution for this.
> 
> 2) In case it gets into the kernel tree, where the 'upstream' will be?
> 
> I have been developing the suite in my github repository [1]. I am planning
> to continue with that, if the suite gets or not into the kernel tree. There
> are still many testcases missing. I also backport the suite for RHEL testing
> purposes.
> 
> It is easier for me to continue the development there and merge bigger
> chunks into the kernel tree, than move all the development here. Is that
> an acceptable model?
> 
> Is there anything else that you would like to point at?

also I think you could erase the  ==== quoted lines, like:

======== base_annotate ========
-- [ PASS ] -- perf_annotate :: setup :: building the example code
-- [ PASS ] -- perf_annotate :: setup :: record data

you have the 'perf_annotate' info in each line, which I assume
is connected to the base_annotate header

jirka

Re: [PATCH 0/9] perf test: the testsuite again

[Jiri Olsa]

On Wed, Mar 16, 2016 at 02:50:06PM +0100, Michael Petlan wrote:
> Hi all,
> 
> after some time, I am sending the proposed testsuite again. I have fixed
> couple of things there since last time.
> 
>   * three verbosity levels are now supported (perf test suite -vv)
>   * logs and temp files are stored in /tmp/, so the main tree is not
>     spoiled anymore
>   * more things can be parametrized from the outside
>   * log parsing should be more robust now
> 
> The testsuite is roughly tested on x86_64, i386, ppc64, s390x and aarch64.
> The following patches should be applicable upon the Arnaldo's tree, to the
> 'perf/core' branch.
> 
> Some issues to be discussed:
> 
> 1) Packaging
> 
> While the other tests are packed within perf, the character of this suite
> does not fit that model very well. Nowadays, it is run only when the dir
> 'testsuite' is found in the current dir. Otherwise the test is skipped.
> I still haven't found any better solution for this.
> 
> 2) In case it gets into the kernel tree, where the 'upstream' will be?
> 
> I have been developing the suite in my github repository [1]. I am planning
> to continue with that, if the suite gets or not into the kernel tree. There
> are still many testcases missing. I also backport the suite for RHEL testing
> purposes.
> 
> It is easier for me to continue the development there and merge bigger
> chunks into the kernel tree, than move all the development here. Is that
> an acceptable model?
> 
> Is there anything else that you would like to point at?

ctrl-c does not stop the suite.. I checked and you run several
command on background.. is there a reason for that?


[jolsa@krava perf]$ sudo ./perf test suite -v
44: Testsuite                                                :
--- start ---
test child forked, pid 25786
======== base_stat ========
-- [ PASS ] -- perf_stat :: test_basic :: basic execution

...

-- [ PASS ] -- perf_annotate :: test_basic :: redirected input
-- [ PASS ] -- perf_annotate :: test_basic :: execution without data
## [ PASS ] ## perf_annotate :: test_basic SUMMARY
## [ SKIP ] ## perf_annotate :: cleanup :: testcase skipped

======== base_report ========
^C
[jolsa@krava perf]$ ^C
[jolsa@krava perf]$ ^C
[jolsa@krava perf]$ -- [ PASS ] -- perf_report :: setup :: prepare the perf.data file
-- [ SKIP ] -- perf_report :: test_basic :: help message :: testcase skipped
-- [ FAIL ] -- perf_report :: test_basic :: basic execution (output regexp parsing)
-- [ FAIL ] -- perf_report :: test_basic :: number of samples (output regexp parsing)
-- [ PASS ] -- perf_report :: test_basic :: header



jirka

Re: [PATCH 0/9] perf test: the testsuite again

[Jiri Olsa]

On Wed, Mar 16, 2016 at 02:50:06PM +0100, Michael Petlan wrote:
> Hi all,
> 
> after some time, I am sending the proposed testsuite again. I have fixed
> couple of things there since last time.
> 
>   * three verbosity levels are now supported (perf test suite -vv)
>   * logs and temp files are stored in /tmp/, so the main tree is not
>     spoiled anymore
>   * more things can be parametrized from the outside
>   * log parsing should be more robust now
> 
> The testsuite is roughly tested on x86_64, i386, ppc64, s390x and aarch64.
> The following patches should be applicable upon the Arnaldo's tree, to the
> 'perf/core' branch.
> 
> Some issues to be discussed:
> 
> 1) Packaging
> 
> While the other tests are packed within perf, the character of this suite
> does not fit that model very well. Nowadays, it is run only when the dir
> 'testsuite' is found in the current dir. Otherwise the test is skipped.
> I still haven't found any better solution for this.
> 
> 2) In case it gets into the kernel tree, where the 'upstream' will be?
> 
> I have been developing the suite in my github repository [1]. I am planning
> to continue with that, if the suite gets or not into the kernel tree. There
> are still many testcases missing. I also backport the suite for RHEL testing
> purposes.
> 
> It is easier for me to continue the development there and merge bigger
> chunks into the kernel tree, than move all the development here. Is that
> an acceptable model?
> 
> Is there anything else that you would like to point at?
> 
> Thanks.
> Michael

so when I run 'sudo perf test suite -v' I assume I'm getting
one test pre line output with status at the begning:

======== base_report ========
-- [ PASS ] -- perf_report :: setup :: prepare the perf.data file
-- [ SKIP ] -- perf_report :: test_basic :: help message :: testcase skipped
-- [ FAIL ] -- perf_report :: test_basic :: basic execution (output regexp parsing)
-- [ FAIL ] -- perf_report :: test_basic :: number of samples (output regexp parsing)
-- [ PASS ] -- perf_report :: test_basic :: header
-- [ FAIL ] -- perf_report :: test_basic :: show CPU utilization (output regexp parsing)
-- [ FAIL ] -- perf_report :: test_basic :: pid (output regexp parsing)
-- [ FAIL ] -- perf_report :: test_basic :: non-existing symbol (output regexp parsing)
-- [ FAIL ] -- perf_report :: test_basic :: symbol filter (output regexp parsing)
## [ FAIL ] ## perf_report :: test_basic SUMMARY :: 6 failures found
## [ SKIP ] ## perf_report :: cleanup :: testcase skipped


that seems great, and it'd be nice if you could frce this 1 line per 
test even if some test fails and spits out some error message, like:

-- [ PASS ] -- perf_probe :: test_listing :: userspace functions list
Failed to find the path for kernel: Invalid ELF file
  Error: Failed to show vars.
-- [ FAIL ] -- perf_probe :: test_listing :: kernel variables list (command exitcode + output regexp parsing)
-- [ PASS ] -- perf_probe :: test_listing :: userspace variables list
Failed to find the path for kernel: Invalid ELF file
  Error: Failed to show lines.
-- [ FAIL ] -- perf_probe :: test_listing :: kernel lines list (command exitcode + output regexp parsing)
Failed to find the path for kernel: Invalid ELF file
  Error: Failed to show lines.
-- [ FAIL ] -- perf_probe :: test_listing :: kernel source lines list (command exitcode + output regexp parsing)
-- [ SKIP ] -- perf_probe :: test_listing :: userspace lines list :: testcase skipped


which breaks otherwise nice output ;-)

jirka

Re: [PATCH 0/9] perf test: the testsuite again

[Michael Petlan]

On Sun, 27 Mar 2016, Jiri Olsa wrote:
> ctrl-c does not stop the suite.. I checked and you run several
> command on background.. is there a reason for that?
>
>
> [jolsa@krava perf]$ sudo ./perf test suite -v
> 44: Testsuite                                                :
> --- start ---
> test child forked, pid 25786
> ======== base_stat ========
> -- [ PASS ] -- perf_stat :: test_basic :: basic execution
>
> ...
>
> -- [ PASS ] -- perf_annotate :: test_basic :: redirected input
> -- [ PASS ] -- perf_annotate :: test_basic :: execution without data
> ## [ PASS ] ## perf_annotate :: test_basic SUMMARY
> ## [ SKIP ] ## perf_annotate :: cleanup :: testcase skipped
>
> ======== base_report ========
> ^C
> [jolsa@krava perf]$ ^C
> [jolsa@krava perf]$ ^C
> [jolsa@krava perf]$ -- [ PASS ] -- perf_report :: setup :: prepare the perf.data file
> -- [ SKIP ] -- perf_report :: test_basic :: help message :: testcase skipped
> -- [ FAIL ] -- perf_report :: test_basic :: basic execution (output regexp parsing)
> -- [ FAIL ] -- perf_report :: test_basic :: number of samples (output regexp parsing)
> -- [ PASS ] -- perf_report :: test_basic :: header
>
>

I think this is a generic behaviour of perf-test itself. In the case of the
testsuite it just has a bigger "race window" you can hit with the C-c.

Every test forks:

---- end ----
roundtrip evsel->name check: Ok
12: Check parsing of sched tracepoints fields                :
--- start ---
test child forked, pid 8304
test child finished with 0
---- end ----
Check parsing of sched tracepoints fields: Ok
13: Generate and check syscalls:sys_enter_openat event fields:
--- start ---
test child forked, pid 8305
mmap size 528384B
test child finished with 0
---- end ----

And I managed to C-c the test 14 hitting the "race window", so it continued
printing something:

14: struct perf_event_attr setup                             :
--- start ---
test child forked, pid 8306
running './tests/attr/test-record-C0'
unsupp  './tests/attr/test-record-C0'
running './tests/attr/test-record-basic'
unsupp  './tests/attr/test-record-basic'
running './tests/attr/test-record-branch-any'
unsupp  './tests/attr/test-record-branch-any'
running './tests/attr/test-record-branch-filter-any'
unsupp  './tests/attr/test-record-branch-filter-any'
running './tests/attr/test-record-branch-filter-any_call'
unsupp  './tests/attr/test-record-branch-filter-any_call'
running './tests/attr/test-record-branch-filter-any_ret'
unsupp  './tests/attr/test-record-branch-filter-any_ret'
running './tests/attr/test-record-branch-filter-hv'
unsupp  './tests/attr/test-record-branch-filter-hv'
running './tests/attr/test-record-branch-filter-ind_call'
unsupp  './tests/attr/test-record-branch-filter-ind_call'
running './tests/attr/test-record-branch-filter-k'
unsupp  './tests/attr/test-record-branch-filter-k'
running './tests/attr/test-record-branch-filter-u'
unsupp  './tests/attr/test-record-branch-filter-u'
running './tests/attr/test-record-count'
unsupp  './tests/attr/test-record-count'
running './tests/attr/test-record-data'
unsupp  './tests/attr/test-record-data'
running './tests/attr/test-record-freq'
unsupp  './tests/attr/test-record-freq'
running './tests/attr/test-record-graph-default'
unsupp  './tests/attr/test-record-graph-default'
running './tests/attr/test-record-graph-dwarf'
unsupp  './tests/attr/test-record-graph-dwarf'
running './tests/attr/test-record-graph-fp'
^C
[root@muflon perf]# sh: line 1:  8357 Terminated              PERF_TEST_ATTR=/tmp/tmpzPprWC ./perf record -o /tmp/tmpzPprWC/perf.data --call-graph fp kill > /dev/null 2>&1
unsupp  './tests/attr/test-record-graph-fp'
running './tests/attr/test-record-group'
unsupp  './tests/attr/test-record-group'
running './tests/attr/test-record-group-sampling'
unsupp  './tests/attr/test-record-group-sampling'
running './tests/attr/test-record-group1'
unsupp  './tests/attr/test-record-group1'

When looking at `ps aux | grep perf | grep -v grep`, you can see the following:

# in this case you won't hit the "race window", C-c would work
root      8286  0.0  0.1  76944  5692 pts/0    S+   18:16   0:00 perf test -v
root      8292  0.0  0.0  81316  3640 pts/0    S+   18:16   0:00 perf test -v

# in this case you hit the "race window" (run ps aux exactly when a sub-test
# was running), so C-c would kill the perf test itself, but not the PID 8307
# (which will continue printing stuff)
root      8286  0.0  0.1  76944  5692 pts/0    S+   18:16   0:00 perf test -v
root      8306  0.0  0.0  76944   936 pts/0    S+   18:16   0:00 perf test -v
root      8307  1.6  0.3 192668 12340 pts/0    D+   18:16   0:00 /usr/bin/python2 ./tests/attr.py -d ./tests/attr/ -p ./perf -v

When the testsuite runs, it usually runs some /bin/bash instead of the python2
here. Since the testsuite spends most of the time in running the subtests outside
of the C code (known issue), your chance that you hit that moment by C-c is pretty
high. I don't think it can be fixed without re-designing the perf-test itself.

Regards,
Michael

>
> jirka
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>