1. 16 3月, 2013 1 次提交
  2. 25 1月, 2013 1 次提交
    • A
      perf tests: Adjust some message log levels to help diagnosing problems in attr tests · ce90e385
      Arnaldo Carvalho de Melo 提交于
      Now we'll see the command being run and if it fails, the fields that had
      unexpected values and the expected values, example testing a problem in the
      next patch:
      
        # perf test -v 13
        13: struct perf_event_attr setup                           :
        --- start ---
        SNIP
          running 'PERF_TEST_ATTR=/tmp/tmpDNIE6M /home/acme/bin/perf record -o /tmp/tmpDNIE6M/perf.data --group -e cycles,instructions kill >/dev/null 2>&1' ret 0
          running 'PERF_TEST_ATTR=/tmp/tmpV5lKro /home/acme/bin/perf stat -o /tmp/tmpV5lKro/perf.data -dd kill >/dev/null 2>&1' ret 1
        expected config=3, got 65540
        expected exclude_guest=1, got 0
        FAILED '/home/acme/libexec/perf-core/tests/attr/test-stat-detailed-2' - match failure
        ---- end ----
        struct perf_event_attr setup: FAILED!
        #
      
      While in the past we would see at the '-v' level many more messages for the
      fields that matched, something we may want to see only in the '-vv' log level.
      
      Keeping the 'running' messages so that we can see the tools tests that
      succeeded so that we can compare it to the one that failed, helping pinpointing
      the command line switch combo that leads to the problem.
      
      Cc: David Ahern <dsahern@gmail.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Jiri Olsa <jolsa@redhat.com>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Namhyung Kim <namhyung@gmail.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Stephane Eranian <eranian@google.com>
      Link: http://lkml.kernel.org/n/tip-9avmwxv5ipxyafwqxbk52ylg@git.kernel.orgSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      ce90e385
  3. 09 11月, 2012 1 次提交
  4. 06 11月, 2012 2 次提交
  5. 01 11月, 2012 1 次提交