lkml.org 
[lkml]   [2021]   [Oct]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [tracing/selftests] cfece71411: kernel-selftests.ftrace.event_trigger_-_test_inter-event_histogram_trigger_onchange_action.fail
    Hi,

    On Fri, 29 Oct 2021 14:48:18 +0800
    kernel test robot <oliver.sang@intel.com> wrote:

    >
    >
    > Greeting,
    >
    > FYI, we noticed the following commit (built with gcc-9):
    >
    > commit: cfece71411dbca5dc5e1fa2d9ce5a3f38e55d4fe ("[PATCH v4 7/8] tracing/selftests: Add tests for hist trigger expression parsing")
    > url: https://github.com/0day-ci/linux/commits/Kalesh-Singh/tracing-Extend-histogram-triggers-expression-parsing/20211026-042529
    >
    >
    > in testcase: kernel-selftests
    > version: kernel-selftests-x86_64-c8c9111a-1_20210929
    > with following parameters:
    >
    > group: ftrace
    > ucode: 0xe2
    >
    > test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
    > test-url: https://www.kernel.org/doc/Documentation/kselftest.txt

    Thanks! This issue has been found and will be fixed next version.

    BTW, I have some questions about this bot;

    >
    >
    > on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz with 32G memory
    >
    > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
    >
    >
    >
    > If you fix the issue, kindly add following tag
    > Reported-by: kernel test robot <oliver.sang@intel.com>
    >
    >
    >
    > TAP version 13
    > 1..1
    > # selftests: ftrace: ftracetest
    > # === Ftrace unit tests ===
    > # [1] Basic trace file check [PASS]
    > ...
    > <<< [1] - [67] have same results as parent, i.e. both PASS or both FAIL >>>

    At first, I guess the robot just checks the "[number]" instead
    of the test description, but the ftracetest doesn't fix the "[number]"
    for each test, Thus, it can be different when updated it.
    So if you compare the result, please check the descriptions too.

    > ...
    > # [67] event trigger - test multiple actions on hist trigger [PASS]
    >
    > >>> [68] - [72] can PASS on parent
    > # [68] event trigger - test inter-event histogram trigger onchange action [FAIL]
    > # [69] event trigger - test inter-event histogram trigger onmatch action [FAIL]
    > # [70] event trigger - test inter-event histogram trigger onmatch-onmax action [FAIL]
    > # [71] event trigger - test inter-event histogram trigger onmax action [FAIL]
    > # [72] event trigger - test inter-event histogram trigger snapshot action [FAIL]
    >
    > >>> [73] fail on parent, too
    > # [73] event trigger - test inter-event histogram trigger eprobe on synthetic event [FAIL]
    >
    > >>> [74] - [92] can PASS on parent
    > # [74] event trigger - test synthetic event create remove [FAIL]
    > # [75] event trigger - test inter-event histogram trigger trace action with dynamic string param [FAIL]
    > # [76] event trigger - test synthetic_events syntax parser [FAIL]
    > # [77] event trigger - test synthetic_events syntax parser errors [FAIL]
    > # [78] event trigger - test inter-event histogram trigger trace action [FAIL]
    > # [79] event trigger - test event enable/disable trigger [FAIL]
    > # [80] event trigger - test trigger filter [FAIL]
    > # [81] event trigger - test histogram expression parsing [FAIL]
    > # [82] event trigger - test histogram modifiers [FAIL]
    > # [83] event trigger - test histogram parser errors [FAIL]
    > # [84] event trigger - test histogram trigger [FAIL]
    > # [85] event trigger - test multiple histogram triggers [FAIL]
    > # [86] event trigger - test snapshot-trigger [FAIL]
    > # [87] event trigger - test stacktrace-trigger [FAIL]
    > # [88] trace_marker trigger - test histogram trigger [FAIL]
    > # [89] trace_marker trigger - test snapshot trigger [FAIL]
    > # [90] trace_marker trigger - test histogram with synthetic event against kernel event [FAIL]
    > # [91] trace_marker trigger - test histogram with synthetic event [FAIL]
    > # [92] event trigger - test traceon/off trigger [FAIL]
    > # [93] (instance) Basic test for tracers [PASS]
    > ...
    > <<< [93] - [112] have same results as parent, all PASS >>>
    > ...
    > # [112] (instance) trace_marker trigger - test histogram trigger [PASS]
    >
    > >>> parent has no [113]
    > # [113] (instance) trace_marker trigger - test snapshot trigger [PASS]

    And next, some patch series may *ADD* new testcases if the series add
    a new feature, so if you find the difference which is not in the
    parent commit but it is passed, please ignore that.

    > # tac: failed to create temporary file in '/tmp/ftracetest-dir.o54lNh': No such file or directory
    > # tac: failed to create temporary file in '/tmp/ftracetest-dir.o54lNh': No such file or directory
    > # tac: failed to create temporary file in '/tmp/ftracetest-dir.o54lNh': No such file or directory
    > # tac: failed to create temporary file in '/tmp/ftracetest-dir.o54lNh': No such file or directory

    And if you find this kind of new error message like above, please report it.
    This is more important for us.

    > #
    > #
    > # # of passed: 85
    > # # of failed: 26
    > # # of unresolved: 1
    > # # of untested: 0
    > # # of unsupported: 0
    > # # of xfailed: 1
    > # # of undefined(test bug): 0
    > not ok 1 selftests: ftrace: ftracetest # exit=1

    Also, please configure your running environment correctly so that all
    ftracetest passes. If you unsure how to do, please ask me.

    Thank you,

    >
    >
    >
    > To reproduce:
    >
    > git clone https://github.com/intel/lkp-tests.git
    > cd lkp-tests
    > sudo bin/lkp install job.yaml # job file is attached in this email
    > bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
    > sudo bin/lkp run generated-yaml-file
    >
    > # if come across any failure that blocks the test,
    > # please remove ~/.lkp and /lkp dir to run from a clean state.
    >
    >
    >
    > ---
    > 0DAY/LKP+ Test Infrastructure Open Source Technology Center
    > https://lists.01.org/hyperkitty/list/lkp@lists.01.org Intel Corporation
    >
    > Thanks,
    > Oliver Sang
    >


    --
    Masami Hiramatsu <mhiramat@kernel.org>

    \
     
     \ /
      Last update: 2021-10-29 14:02    [W:3.544 / U:0.076 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site