New issue
Advanced search Search tips

Issue 907174 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Build-Toolchain


Participants' hotlists:
bugsincrosperf


Sign in to add a comment

[crosperf] Profiling failed with recent version of crosperf

Project Member Reported by tcwang@chromium.org, Nov 20

Issue description

To reproduce the bug:

In the crosperf script, pass some profiling arguments of perf record: perf_args: record ...

(Actually no perf record argument can still cause the problem because -a is added by default)

Use release image of caroline: 
build: caroline-release/R72-11280.0.0

(I tested on caroline DUT)

Then test speedometer2.

The output shows the benchmark finishes without any problem. But there's no profiling data collected, and the error message is like this:

==========================================================================
WARNING: The /tmp/test_that_results_YHuB5G/results-1-telemetry_Crosperf/telemetry_Crosperf/profiling/perf.data file's data size field is 0 which is unexpected.
Was the 'perf record' command properly terminated?
Warning:
Kernel address maps (/proc/{kallsyms,modules}) were restricted.

Check /proc/sys/kernel/kptr_restrict before running 'perf record'.

As no suitable kallsyms nor vmlinux was found, kernel samples
can't be resolved.

Samples in kernel modules can't be resolved as well.

Error:
The /tmp/test_that_results_YHuB5G/results-1-telemetry_Crosperf/telemetry_Crosperf/profiling/perf.data file has no samples!

==============================================================================

I have tested that valid perf data can be collected by manually executing perf record while running the benchmark.

 
Description: Show this description
Please attach experiment file and show the exact command used to run crosperf.  Thanks!
Labels: OS-Chrome
exp file is attached. The command I used to run crosperf is:

crosperf /path/to/caroline_perf_histo.exp  --rerun=True --logging_level=verbose --locks_dir=/tmp --use_file_locks=True --no_email=True
caroline_perf_histo.exp
300 bytes Download
Status: Started (was: Assigned)
Labels: -Pri-3 Pri-2
Project Member

Comment 7 by bugdroid1@chromium.org, Dec 1

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/52754b48a20c54177bd2f08755bf57f2988e1177

commit 52754b48a20c54177bd2f08755bf57f2988e1177
Author: Zhizhou Yang <zhizhouy@google.com>
Date: Sat Dec 01 23:44:22 2018

telemetry_Crosperf: Fix failure collecting perf data on release img

Killall command on release image cannot recognize -INT. This patch
replaces -INT with -2 to make it work on release image.

BUG= chromium:907174 
TEST=Tested using edgar and caroline release image.

Change-Id: I6bdd826232cc04a11cb767caee8c49c1db9a08d2
Reviewed-on: https://chromium-review.googlesource.com/1356059
Commit-Ready: Zhizhou Yang <zhizhouy@google.com>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Reviewed-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>

[modify] https://crrev.com/52754b48a20c54177bd2f08755bf57f2988e1177/server/site_tests/telemetry_Crosperf/telemetry_Crosperf.py

Status: Fixed (was: Started)

Sign in to add a comment