Sam Clegg
unread,Nov 8, 2013, 12:33:53 PM11/8/13Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to j...@chromium.org, Lei Zhang, Nico Weber, Michael Moss, Chromium-dev, c...@chromium.org, jo...@chromium.org, Jorge Lucangeli Obes, Isaac Levy, Paweł Hajdan, Jr.
On Mon, Nov 4, 2013 at 10:43 PM, Julien Tinnes <
j...@chromium.org> wrote:
> Yeah, it's supposed to work since last Wednesday, see
>
crbug.com/312572, but there are always bots that aren't updated for
> some reason. Isaac reverted it a few minutes ago.
>
> I thought that John had double-checked that it was installed on all
> bots. Try bots seem to be the issue, the main WF is fine (it was even
> in LKGR).
>
> Nico: can you please report your failing bots to the bug?
>
> John/Chase: any way out of this situation ? It looks like we're not
> equipped to handle new packages, which is problematic. Hopefully this
> can be fixed very soon, I'm really blocked.
> In the medium term, should we switch everything to use sysroot?
I like the idea of always using a sysroot on the bots. We already do
this for the official builders IIUC. Seems like a lot of advantages:
- reduce the bot maintenance burden.
- less dependence on the state of the bot.
- more reproducible builds/failures.
- makes it possible to build two branches with mutually conflicting
deps (e.g. different versions of the same -dev package).
Might even make sense to make this the default for all linux builds
including local devleoper builds. No more PSA messages about having
to run install-build-deps.