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

Issue 686216 link

Starred by 1 user
Status: Started
Owner:
█ pras...@chromium.org
Last visit 27 days ago
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Fix signed chrome bisect for release builds for N and above

Project Member Reported by aluo@chromium.org, Jan 27 2017 
Currently the bisect-archived-builds.py script is using the Monochrome.apk file for this, but for signed bucket, it should use the MonochromeStable.apk.  For unsigned bucket, both Monochrome.apk and MonochromeStable.apk are present, so we should just stick with MonochromeStable.apk for both signed and unsigned.  Users encounter the not enough builds to bisect error for this.

Comment 1 by aluo@chromium.org, Feb 3 2017 

Also need to enable overinstall for MonoochromeStable.apk too in ClankBuild.Install, otherwise adb uninstall fails since it's system app.

Comment 2 by pras...@chromium.org, Feb 3 2017

Status: Started (was: Untriaged)
I think if you pass --apk=chrome_stable instead of "chrome" in the commandline, the script should pickup MonochromeStable.apk.
Let me know if this doesn't work.

Comment 3 by aluo@chromium.org, Feb 3 2017 

will use chrome_stable, just need to address the overinstall issue now on N.
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 1 2017 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/clank/internal/apps/+/aa5ced40106509d0d2be4095cf51bf3d7368c439

commit aa5ced40106509d0d2be4095cf51bf3d7368c439
Author: prasadv <prasadv@google.com>
Date: Wed Mar 01 22:37:11 2017
►

Sign in to add a comment