GTK bots back on the main waterfall, next few weeks will be a bit bumpy

[Nico Weber]

Hi,

we won't ship aura on linux in m34, so we need to ship gtk for m34. To be able to do that, we need to be able to compile the gtk port at least until the m34 branch is cut.

Switching the default from aura to non-aura historically takes 12+ hours, so we don't want to do this twice. So instead we added a single explicit gtk bot to the main waterfall. Sadly, there are no gtk trybots at the moment (it looks like `git cl try` sends jobs to both linux_rel and linux_aura, both of which build aura at the moment, so it looks like we have the resources for gtk trybots. I'll look into this tomorrow.)

So I suggest we treat the linux gtk main waterfall bot like we treated the clang bots in the days of yore: They close the tree, but sheriffs should reopen again if only those bots are red, and people who break the gtk bots can fix them while the tree is open.

It's not ideal, but it's only for a short while.

Thanks for bearing with us,

Nico

[Paweł Hajdan, Jr.]

Thank you for working on this. Also note existing https://code.google.com/p/chromium/issues/detail?id=336581 for any future related changes.

Please make sure to keep LKGR in sync with the main waterfall, and if possible having trybot+CQ coverage as the next steps would be great.

Paweł

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.