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.chromium.org/developers/try-server-usage#TOC-LKGR M-A On Tue, Jul 7, 2009 at 2:11 PM, Darin Fisher <darin@chromium.org> wrote:
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 community since it may turn red due to non-WebKit related changes.
Thanks for thinking of us! -Darin
On Tue, Jul 7, 2009 at 8:56 AM, Eric Carlson <eric.carlson@apple.com>wrote:
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 element backends are, by definition, platform specific it is easy to miss something. I always watch the build bots after a check-in so I can fix things, but that doesn't help me with your builds.
eric
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev