New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 616893 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Can't get systrace with adb_profile_chrome

Project Member Reported by vmi...@chromium.org, Jun 2 2016

Issue description

Device: Nexus 6P (userdebug)
Version: r396555

adb_profile_chrome with '-s' systrace option always fails for me.

$ ./build/android/adb_profile_chrome -b chromium -t 5 -s freq idle am
Capturing 5-second chrome trace + systrace. Press Enter to stop early...
CRITICAL:root:STDERR: ** daemon still not running
error: cannot connect to daemon

^C
Traceback (most recent call last):
  <module> at /usr/local/google/code/chrome/src/third_party/catapult/systrace/bin/adb_profile_chrome:14
    sys.exit(main.main())
  main at /usr/local/google/code/chrome/src/third_party/catapult/systrace/profile_chrome/main.py:253
    write_json=options.json)
  CaptureProfile at /usr/local/google/code/chrome/src/third_party/catapult/systrace/profile_chrome/profiler.py:84
    _StopTracing(controllers)
  _StopTracing at /usr/local/google/code/chrome/src/third_party/catapult/systrace/profile_chrome/profiler.py:20
    controller.StopTracing()
  StopTracing at /usr/local/google/code/chrome/src/third_party/catapult/systrace/profile_chrome/chrome_controller.py:97
    self._trace_finish_re, timeout=120).group(1)
  timeout_retry_wrapper at /usr/local/google/code/chrome/src/third_party/catapult/devil/devil/android/decorators.py:57
    retry_if_func=retry_if_func)
  Run at /usr/local/google/code/chrome/src/third_party/catapult/devil/devil/utils/timeout_retry.py:167
    error_log_func=error_log_func)
  JoinAll at /usr/local/google/code/chrome/src/third_party/catapult/devil/devil/utils/reraiser_thread.py:186
    self._JoinAll(watcher, timeout)
  _JoinAll at /usr/local/google/code/chrome/src/third_party/catapult/devil/devil/utils/reraiser_thread.py:153
    thread.join(0.1)
  join at /usr/lib/python2.7/threading.py:960
    self.__block.wait(delay)
  wait at /usr/lib/python2.7/threading.py:358
    _sleep(delay)
KeyboardInterrupt

Locals:
  delay       : 0.008
  endtime     : 1464901466.5943508
  gotit       : False
  remaining   : 0.09278488159179688
  saved_state : None
  timeout     : 0.09999990463256836
  waiter      : <thread.lock object at 0x7fc54e1c4f90>

^C^C^C^CCRITICAL:root:STDERR: ** daemon still not running
 
Cc: sullivan@chromium.org
Cc: zh...@chromium.org
Zhen, would you be able to take a look?

Comment 3 by zh...@chromium.org, Jun 2 2016

From the error message, it seems adb is not working correctly. Can you run other adb commands successfully? Maybe restart adb server and try again?
I can run adb.  This seems to me like there's an issue with the version of adb used.  Is there something I can do to help diagnose the issue?
Are you running this on Mac or Linux? IIRC, devil lib doesn't seem to support Mac at the moment.
Running on Linux.

Comment 7 by zh...@chromium.org, Jun 6 2016

Just tried your command on ubuntu and Nexus 7 Android 6.0.1 with r396647. It works fine.

Ned, does devil lib use some adb pulled by itself or it uses whatever adb set by the developer on the machine?
Cc: jbudorick@chromium.org
John: can you answer Zhen's question in #7?
It uses its own unless (for legacy compatibility reasons) you have ADB_PATH set in your environment.
... and you should be able to see that in $CATAPULT_ROOT/devil/bin/deps/linux2/x86_64/bin/adb (i.e., in chromium, //third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb)
I see. Thanks John!

Victor, can you check if you set ADB_PATH and try the adb specified by in comment 10?
Components: Test>Telemetry
Components: -Tests>Telemetry

Sign in to add a comment