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

Issue 777983 link

Starred by 1 user
Status: Fixed
Owner:
█ gkihumba@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Cc:
█ josa...@chromium.org
█ bhthompson@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

R63 branch picks up ToT Android instead of m63 branch

Project Member Reported by norvez@chromium.org, Oct 24 2017 

See for example https://luci-milo.appspot.com/buildbot/chromeos_release/cave-release%20release-R63-10032.B/12

The AndroidMetada stage shows the builder is picking up git_nyc-mr1-arc, not -m63

Comment 1 by bhthompson@google.com, Oct 24 2017 

I think the CL to switch over the Android branch may not have landed.

https://chromium-review.googlesource.com/#/c/chromiumos/chromite/+/721921/

Comment 2 by bhthompson@google.com, Oct 24 2017

Owner: gkihumba@chromium.org

Comment 3 by bhthompson@google.com, Oct 24 2017

Cc: bhthompson@chromium.org

Comment 4 by norvez@chromium.org, Oct 25 2017

Status: Fixed (was: Unconfirmed)
It's picking the right branch now: https://luci-milo.appspot.com/buildbot/chromeos_release/cave-release%20release-R63-10032.B/13

Comment 5 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 6 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)
►

Sign in to add a comment