That's a good point... Unfortunately, the integration builder really needs
to see HEAD chromium since we're frequently rolling DEPS to pick up the
latest WebKit tip-of-tree. Seeing any bustage related to such updates is
important. Perhaps a LKGR bot could be useful as an additional bot.
-Darin
An hypothetical chromium builder should sync to
http://chromium-status.appspot.com/lkgr instead of HEAD. That'd fix most of
the "builder failed to compile because chromium tree is broken".
lkgr stands for *last known good revision* in its weakest meaning. If
curious, more info at
http://dev.chromi
We are working on it. It is taking more time than we'd like :-(
For now, we only have an integration builder that tests tip-of-tree WebKit
in a Chromium build environment: http://tinyurl.com/l9mops
That's a big help to Chromium developers, but it isn't something well suited
for the WebKit communi
Chrome hackers -
When do you plan to have a build bot on build.webkit.org?
I broke your build yesterday with http://trac.webkit.org/changeset/45572
, but didn't realize it so Albert had to clean up after me (again,
thanks Albert).
I *try* not to break other builds but the media elemen
4 matches
Mail list logo
