On Mon, Dec 07, 2015 at 07:52:59PM +0100, Michael Petlan wrote:
> In order to be able to run the bash/subcommand-based testsuite directly
> from perf test a new perf-test entry has been created for it.
>
> The driver (suite.c) runs all the tests that it finds in the testsuite
> directory: tools/perf/testsuite/ (rather ./testsuite as it expects it
> it being run from the perf's directory).
>
> In case the testsuite is not found, the testcase is skipped. If this is
> not the desired behaviour, some packaging will be needed.
>
> Usage:
> ./perf test suite
>
> or
> ./perf test suite -v
so -v has following output now:
--- SNIP
[jolsa@krava perf]$ sudo ./perf test suite -v
38: Testsuite :
--- start ---
test child forked, pid 11670
======== base_annotate ========
-- [ PASS ] -- perf_annotate :: setup :: building the example code
Line did not match any pattern: "Lowering default frequency rate to
2000."
Line did not match any pattern: "Please consider tweaking
/proc/sys/kernel/perf_event_max_sample_rate."
-- [ FAIL ] -- perf_annotate :: setup :: record data (output regexp
parsing)
## [ FAIL ] ## perf_annotate :: setup SUMMARY :: 1 failures found
-- [ SKIP ] -- perf_annotate :: test_basic :: help message :: testcase
skipped
-- [ PASS ] -- perf_annotate :: test_basic :: basic execution - annotate
-- [ PASS ] -- perf_annotate :: test_basic :: dso filter
-- [ PASS ] -- perf_annotate :: test_basic :: no-source
-- [ PASS ] -- perf_annotate :: test_basic :: full-paths
-- [ PASS ] -- perf_annotate :: test_basic :: print-line
-- [ PASS ] -- perf_annotate :: test_basic :: redirected input
-- [ PASS ] -- perf_annotate :: test_basic :: execution without data
## [ PASS ] ## perf_annotate :: test_basic SUMMARY
-- [ PASS ] -- perf_annotate :: cleanup :: clean-up logs
======== base_buildid ========
## [ PASS ] ## perf_buildid-cache :: setup SUMMARY
-- [ SKIP ] -- perf_buildid-cache :: test_buildid-list :: help message
:: testcase skipped
Line did not match any pattern:
"2e228243285efef5d8b66c729703b4aebdd12c86 [kernel.kallsyms]"
Line did not match any pattern:
"b5105437a54662622e6d461cf3036e79e9261f4f [vdso]"
Usage: file [-bcEhikLlNnprsvz0] [--apple] [--mime-encoding]
[--mime-type]
[-e testname] [-F separator] [-f namefile] [-m magicfiles]
file ...
file -C [-m magicfiles]
file [--help]
Usage: file [-bcEhikLlNnprsvz0] [--apple] [--mime-encoding]
[--mime-type]
[-e testname] [-F separator] [-f namefile] [-m magicfiles]
file ...
file -C [-m magicfiles]
file [--help]
-- [ FAIL ] -- perf_buildid-cache :: test_buildid-list :: buildids
check (output regexp parsing)
...
--- SNIP
could you ensure following output:
[jolsa@krava perf]$ sudo ./perf test suite
38: Testsuite : FAILED!
[jolsa@krava perf]$ sudo ./perf test suite -v
38: Testsuite :
--- start ---
test child forked, pid 11670
-- [ PASS ] -- perf_annotate :: setup :: building the example code
-- [ FAIL ] -- perf_annotate :: setup :: record data (output regexp
parsing)
## [ FAIL ] ## perf_annotate :: setup SUMMARY :: 1 failures found
-- [ SKIP ] -- perf_annotate :: test_basic :: help message :: testcase
skipped
-- [ PASS ] -- perf_annotate :: test_basic :: basic execution - annotate
-- [ PASS ] -- perf_annotate :: test_basic :: dso filter
-- [ PASS ] -- perf_annotate :: test_basic :: no-source
-- [ PASS ] -- perf_annotate :: test_basic :: full-paths
-- [ PASS ] -- perf_annotate :: test_basic :: print-line
-- [ PASS ] -- perf_annotate :: test_basic :: redirected input
-- [ PASS ] -- perf_annotate :: test_basic :: execution without data
## [ PASS ] ## perf_annotate :: test_basic SUMMARY
-- [ PASS ] -- perf_annotate :: cleanup :: clean-up logs
## [ PASS ] ## perf_buildid-cache :: setup SUMMARY
-- [ SKIP ] -- perf_buildid-cache :: test_buildid-list :: help message
:: testcase skipped
-- [ FAIL ] -- perf_buildid-cache :: test_buildid-list :: buildids
check (output regexp parsing)
...
[jolsa@krava perf]$ sudo ./perf test suite -vv
unleash the hell ;-)
or even add -vvv ... would be suite developers choice anyway ;-)
thanks,
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
