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

Issue 721684 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

"Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR" when trying to symbolize stack

Project Member Reported by perezju@chromium.org, May 12 2017

Issue description

On this recently swarmed android perf bot at:
https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus5X%20Perf

When there are failures and Telemetry tries to see if there are stacks to symbolize in the logcat, the script to symbolize fails with:

Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/android_platform/development/scripts/stack", line 240, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/b/swarming/w/ir/third_party/android_platform/development/scripts/stack", line 196, in main
    constants.CheckOutputDirectory()
  File "/b/swarming/w/ir/third_party/android_platform/development/scripts/../../../../build/android/pylib/constants/__init__.py", line 208, in CheckOutputDirectory
    raise Exception('Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR '
Exception: Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR has been set

https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5X_Perf%2F24%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.common_mobile_on_Android%2F0%2Fstdout

The invocation to the symbolize script happens at:
https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/platform/android_platform_backend.py?rcl=9e43159fc62c2ba87c5dd5202e38aeb5e207bb68&l=741

We should (either or both):

1. Don't attempt to symbolize anything if there appears to be nothing to symbolize on the logcat (maybe something a quick regex can check?)

2. Make sure that symbolize script works on this new swarmed bot 
 
Owner: mikec...@chromium.org
Status: Started (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9ff9c3196bb331d8b97089e61b19888bbe75cfb5

commit 9ff9c3196bb331d8b97089e61b19888bbe75cfb5
Author: catapult-deps-roller@chromium.org <catapult-deps-roller@chromium.org>
Date: Tue Jun 13 00:38:37 2017

Roll src/third_party/catapult/ e663166b9..ceedebe21 (3 commits)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/e663166b9cf3..ceedebe21711

$ git log e663166b9..ceedebe21 --date=short --no-merges --format='%ad %ae %s'
2017-06-12 martiniss Add webview embedded apk flag.
2017-06-12 mikecase Pass output-dir argument to stack script.
2017-06-12 mikecase Adds option to not have SetLogLevel add a log handler.

Created with:
  roll-dep src/third_party/catapult
BUG= 725695 ,721684


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I0eba150a1a220ca44e6ef346dd6c1ec08df3526b
Reviewed-on: https://chromium-review.googlesource.com/531837
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#478843}
[modify] https://crrev.com/9ff9c3196bb331d8b97089e61b19888bbe75cfb5/DEPS

Sign in to add a comment