New issue
Advanced search Search tips

Issue 812526 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 809312
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Binhosts are selected (almost) randomly

Project Member Reported by nya@chromium.org, Feb 15 2018

Issue description

We specify multiple binhosts in make.conf.board (e.g. those from $ARCH-generic-paladin, $BOARD-paladin, and chrome-pfq). But those binhosts are treated equally and not prioritized; when multiple matching binary packages are found, Portage just picks one with the most recent build timestamp. This ends up picking binary packages from multiple binhosts almost randomly, triggering source build.

 

Comment 1 by vapier@chromium.org, Feb 15 2018

Mergedinto: 809312
Status: Duplicate (was: Started)

Sign in to add a comment