Hi -
Trying perf test on llct-based 3.10-rc6 isn't entirely happy.
root@aa9-eb:~# perf test 1: vmlinux symtab matches kallsyms : FAILED! 2: detect open syscall event : Ok 3: detect open syscall event on all cpus : Ok 4: read samples using the mmap interface : Ok 5: parse events tests : Warning: function sizeof not defined Warning: function sizeof not defined Warning: function scsi_trace_parse_cdb not defined Warning: function scsi_trace_parse_cdb not defined Warning: function scsi_trace_parse_cdb not defined Warning: function scsi_trace_parse_cdb not defined Warning: function jiffies_to_msecs not defined Warning: function jiffies_to_msecs not defined Warning: bad op token { Warning: bad op token { Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: bad op token { Warning: bad op token { Warning: bad op token { Warning: bad op token { Warning: unknown op '{' Warning: unknown op '{' Ok 6: Validate PERF_RECORD_* events & perf_sample fields : FAILED! 7: Test perf pmu format parsing : Ok 8: Test dso data interface : Ok 9: roundtrip evsel->name check : Ok 10: Check parsing of sched tracepoints fields : FAILED! 11: Generate and check syscalls:sys_enter_open event fields: Ok 12: struct perf_event_attr setup : (omitted) Ok 13: Test matching and linking mutliple hists : Ok 14: Try 'use perf' in python, checking link problems : FAILED! 15: Test breakpoint overflow signal handler : FAILED! 16: Test breakpoint overflow sampling : FAILED! 17: Test number of exit event of a simple workload : FAILED! 18: Test software clock events have valid period values : Ok
I started tracing the first failure... it stops because it can't find "_stext" in /proc/kallsyms. But it is there
root@aa9-eb:~# cat /proc/kallsyms | grep _stext 800081c0 T _stext
test 5 (parse event tests) seems to be badly broken.
Is this just our problem or is it broken for everyone?
-Andy
On 26 June 2013 09:16, Andy Green andy.green@linaro.org wrote:
test 5 (parse event tests) seems to be badly broken.
Is this just our problem or is it broken for everyone?
I'm not sure if the reason is the same but this test was broken in LAVA for some time now. The latest result on 3.10.0-1-linaro-omap kernel looks like this:
perf test - parse events tests :Can't open event dir : No such file or directory Can't open event dir : No such file or directory Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : function jiffies_to_msecs not defined Warning : function jiffies_to_msecs not defined Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : unknown op '{' Warning : unknown op '{' FAIL
milosz
On 26 June 2013 17:57, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On 26 June 2013 09:16, Andy Green andy.green@linaro.org wrote:
Hi Milosz -
test 5 (parse event tests) seems to be badly broken.
Is this just our problem or is it broken for everyone?
I'm not sure if the reason is the same but this test was broken in LAVA for some time now. The latest result on 3.10.0-1-linaro-omap kernel looks like this:
perf test - parse events tests :Can't open event dir : No such file or directory Can't open event dir : No such file or directory Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : function jiffies_to_msecs not defined Warning : function jiffies_to_msecs not defined Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : unknown op '{' Warning : unknown op '{' FAIL
Thanks.
I guess it is simply broken upstream, or we missed a point somewhere.
Llct does have one patch compared to vanilla 3.10-rc6 but that's it
diff --git a/tools/perf/config/utilities.mak b/tools/perf/config/utilities.mak index 8ef3bd3..3e89719 100644 --- a/tools/perf/config/utilities.mak +++ b/tools/perf/config/utilities.mak @@ -173,7 +173,7 @@ _ge-abspath = $(if $(is-executable),$(1)) # Usage: absolute-executable-path-or-empty = $(call get-executable-or-default,variable,default) # define get-executable-or-default -$(if $($(1)),$(call _ge_attempt,$($(1)),$(1)),$(call _ge_attempt,$(2),$(1))) +$(if $($(1)),$(call _ge_attempt,$($(1)),$(1)),$(call _ge_attempt,$(2))) endef _ge_attempt = $(if $(get-executable),$(get-executable),$(_gea_warn)$(call _gea_err,$(2))) _gea_warn = $(warning The path '$(1)' is not executable.)
What's the plan for tests that are in Lava that are themselves partially broken? We should snip or force the results, patch to turn off those tests?
-Andy
On 26 June 2013 11:42, Andy Green andy.green@linaro.org wrote:
On 26 June 2013 17:57, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On 26 June 2013 09:16, Andy Green andy.green@linaro.org wrote:
Hi Milosz -
test 5 (parse event tests) seems to be badly broken.
Is this just our problem or is it broken for everyone?
I'm not sure if the reason is the same but this test was broken in LAVA for some time now. The latest result on 3.10.0-1-linaro-omap kernel looks like this:
perf test - parse events tests :Can't open event dir : No such file or directory Can't open event dir : No such file or directory Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : function scsi_trace_parse_cdb not defined Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : function jiffies_to_msecs not defined Warning : function jiffies_to_msecs not defined Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : Error : expected type 4 but read 0 Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : bad op token { Warning : unknown op '{' Warning : unknown op '{' FAIL
Thanks.
I guess it is simply broken upstream, or we missed a point somewhere.
Llct does have one patch compared to vanilla 3.10-rc6 but that's it
diff --git a/tools/perf/config/utilities.mak b/tools/perf/config/utilities.mak index 8ef3bd3..3e89719 100644 --- a/tools/perf/config/utilities.mak +++ b/tools/perf/config/utilities.mak @@ -173,7 +173,7 @@ _ge-abspath = $(if $(is-executable),$(1)) # Usage: absolute-executable-path-or-empty = $(call get-executable-or-default,variable,default) # define get-executable-or-default -$(if $($(1)),$(call _ge_attempt,$($(1)),$(1)),$(call _ge_attempt,$(2),$(1))) +$(if $($(1)),$(call _ge_attempt,$($(1)),$(1)),$(call _ge_attempt,$(2))) endef _ge_attempt = $(if $(get-executable),$(get-executable),$(_gea_warn)$(call _gea_err,$(2))) _gea_warn = $(warning The path '$(1)' is not executable.)
What's the plan for tests that are in Lava that are themselves partially broken? We should snip or force the results, patch to turn off those tests?
I don't think it is a good idea to disable tests that are broken. I would rather see them fixed. There are more test cases run in LAVA that fail due to different reasons.
milosz
-
Andy Green -
Milosz Wasilewski