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

Issue 597771 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

WebView Bisect bot fails on "logcat dump" step when attempting to bisect.

Project Member Reported by mikec...@chromium.org, Mar 24 2016

Issue description

Example, https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_aosp_perf_bisect/builds/78


Traceback (most recent call last):
  File "/b/build/slave/android_webview_aosp_perf_bisect/build/src/build/android/adb_logcat_printer.py", line 213, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/b/build/slave/android_webview_aosp_perf_bisect/build/src/build/android/adb_logcat_printer.py", line 163, in main
    output_file = open(options.output_path, 'w')
IOError: [Errno 2] No such file or directory: '/b/build/slave/android_webview_aosp_perf_bisect/build/src/out/Release/full_log'
step returned non-zero exit code: 1
@@@STEP_EXCEPTION@@@


 
Owner: martiniss@chromium.org
Status: Assigned (was: Untriaged)
It looks like it's not compiling or running any tests, and so no log is being generated...

It does provision devices, and all that, and then doesn't do anything.
hmmm, bisects worked on this bot less than a month ago. Maybe some change was made to the bisect recipe that broke the webview bisecting completely?
I'm not familiar with the recipes enough to determine why nothing is being done. One thing you might want to consider is that it appears that the bot is configured to use mb, and not gyp (see bottom of https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_aosp_perf_bisect/builds/78/steps/gclient%20runhooks/logs/stdio).
Cc: pras...@chromium.org robert...@chromium.org martiniss@chromium.org
Owner: ----
Status: Available (was: Assigned)
Don't think this is solvable by infra; I'll stay on the bug though. I've cc-ed people who work on the bisect recipe. 
Issue 597457 has been merged into this issue.
According to step #15 on https://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_cq/builds/84 the lack of tests seem to be WAI. We should add a check to the script that collects the logcats to exit quietly if there are no logs.
Owner: bpastene@chromium.org
Status: Assigned (was: Available)
... which is something that I'll do
Project Member

Comment 8 by bugdroid1@chromium.org, Mar 25 2016

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

commit 0c5d30d1932954a34d417bf1f195ac1428d5aeed
Author: bpastene <bpastene@chromium.org>
Date: Fri Mar 25 19:30:24 2016

Create output dir in logcat printer if it doesn't exist.

Also add a statement about where to find the actual logcat.

BUG= 597771 , 448050 

Review URL: https://codereview.chromium.org/1838483002

Cr-Commit-Position: refs/heads/master@{#383330}

[modify] https://crrev.com/0c5d30d1932954a34d417bf1f195ac1428d5aeed/build/android/adb_logcat_printer.py

Comment 9 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>Android
Labels: -Infra-Android
Status: Fixed (was: Assigned)
This type of failure should be fixed now.

Sign in to add a comment