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

Issue 695771 link

Starred by 2 users
Status: WontFix
Owner:
█ yunlian@chromium.org
Last visit > 30 days ago
Closed: Mar 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

paladin builders setup for LLVM migration are still failing

Project Member Reported by llozano@chromium.org, Feb 24 2017 
The following CL introduced some PFQ and paladin builders to enable some LLVM testing

https://chromium-review.googlesource.com/443073

However, some of them are failing in build_packages phase.
Fortunately, they are marked as "experimental' so they don't seem to be blocking anything.

so, the following are failing

peach_pi-paladin
squawks-paladin
terra-paladin
veyron_jaq-paladin

and, interestingly, veyron_peppy is passing.

Comment 1 by yunlian@chromium.org, Feb 24 2017 

They all complains that they could not find chromeos-chrome prebuilts, it is probably because the chrome master pfq has not passed once since the builder starts.

Comment 2 by llozano@chromium.org, Feb 24 2017 

i believe the master-pfq has passed for veyron_jaq .. so why is that one complainign?

Comment 3 by yunlian@chromium.org, Feb 24 2017 

The master-pfq has been red since Feb 13. 
However, I see some manual update for Chrome.
In change
commit 4cd5e4cba423029d694e249c8ab4e76b96f25fa1

Besides modifying the ebuilds, it also modifies the file
src/third_party/chromiumos-overlay/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf

I am not sure whether we need to do this for our chromium buildbot.

Comment 4 by yunlian@chromium.org, Feb 24 2017 

It seems in the binhost stage, it does not get the profiles for experimental pfqs.

Comment 5 by yunlian@chromium.org, Mar 8 2017

Status: WontFix (was: Assigned)
We do not need these temporary buildbots anymore.
►

Sign in to add a comment