On 26 June 2013 11:42, Andy Green <andy.gr...@linaro.org> wrote:
> On 26 June 2013 17:57, Milosz Wasilewski <milosz.wasilew...@linaro.org> wrote:
>> On 26 June 2013 09:16, Andy Green <andy.gr...@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
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
