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

Issue 689602 link

Starred by 1 user
Status: Fixed
Owner:
█ pschmidt@chromium.org
Last visit > 30 days ago
Closed: Feb 2017
Cc:
█ kbr@chromium.org
█ pschmidt@chromium.org
jo...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Upgrade Nexus 9 bot on GPU FYI waterfall to Android M

Project Member Reported by zmo@chromium.org, Feb 7 2017

Comment 1 by zmo@chromium.org, Feb 7 2017

Components: Infra>Labs
kbr, can you help finding an owner?

Since both Pixel C and Nexus 9 use the same GPU, if they are on different driver versions, for which our test expectations don't handle, it creates confusion in test suppression.

Comment 2 by kbr@chromium.org, Feb 7 2017

Cc: jo...@chromium.org pschmidt@chromium.org
Peter or John, could you help us with this upgrade? Thanks.

Comment 3 by pschm...@google.com, Feb 7 2017

Owner: pschmidt@chromium.org
Status: Assigned (was: Available)
I can do this.

Comment 4 by pschmidt@chromium.org, Feb 8 2017

Status: Fixed. (was: Assigned)
The Pixel-C has google/ryu/dragon:6.0.1/MXC89L/3084571:userdebug/dev-keys   There is no such release for volantis.

Installed MOB31L on the Nexus 9 as it's also a 6.0.1 variant and we had it already set up on our flashing station.

chrome-bot@build61-b1:(Linux 14.04):~$ ./adb -d shell getprop ro.build.fingerprint
google/volantis/flounder:6.0.1/MOB31L/3383703:userdebug/dev-keys

Comment 5 by zmo@chromium.org, Feb 8 2017 

Thank you, Peter.

Comment 6 by pschmidt@chromium.org, Feb 9 2017

Status: Fixed (was: Fixed.)
►

Sign in to add a comment