Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 1 user
Status: Verified
Owner:
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment
[VMTest] cheets_CTS.6.0_r14.x86.android.core.tests.libcore.package.harmony_java_math fails on cyan-tot-chrome-pfq-informational
Project Member Reported by warx@chromium.org, Jan 25 2017 Back to list
Cc: levarum@chromium.org
Owner: lhchavez@chromium.org
Luis says he need to cherry-pick some CLs from nyc to mnc to fix this.
Cc: hidehiko@chromium.org
Status: Started
This change https://codereview.chromium.org/2583263002 needs an Android-side change that was merged to one of the branches, but not mnc.

Cherry-picking both of those changes makes adb connect again.
Dumb sheriff question: Is it faster to fix the chrome tot informational bots by fixing Android side, or by reverting chrome-side change?

(I'm not sure how the cyan-tot-chrome-pfq-informational bot gets its revision of android.)

Probably faster by fixing it in Android. There have been other changes that took dependency on this on Chrome side :(
Status: Fixed
This should be fixed with ARC 3674904 (or above).
How long does it take for Android changes to roll into chrome-pfq builders?
If everything goes well, the 3p build of https://uberchromegw.corp.google.com/i/chromeos/builders/master-android-pfq should include the new changes. Those runs take between 30 minutes and 3h to finish, so w.c.s. by 6p today we should have the fixed bits.
ARGH the Android PFQ finished ~20 minutes later than expected https://uberchromegw.corp.google.com/i/chromeos/builders/master-android-pfq/builds/2208

The current informational build did not get a chance to pick up the changes https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/cyan-tot-chrome-pfq-informational/builds/1588, but the very next one should.
Sign in to add a comment