> - run the tests on our webkit canary bot (should be doable) Yes, that would be handy. We need a combination of ToT Chromium + ToT WebKit to be checked. That way, we will have a chance to fix thinks before they break the build during WebKit deps roll.
We know that the ideal solution would be to have all the stuff upstreamed to WebKit, so commits that break Dev Tools would break WebKit, and thus got rolled back or quickly fixed. We are trying to upstream as much things as possible, but currently it seems unavoidable to have some Chromium-specific code which depends on WebKit Inspector implementation. I think, Pavel could give more concrete examples after he get back from vacation. On Sat, Sep 12, 2009 at 04:46, Paweł Hajdan Jr. <[email protected]> wrote: > DevToolsSanityTest flips frequently between enabled and disabled. It seems > to be mostly caused by changes in WebKit. I see two nice ways to prevent > that: > - run the tests upstream on webkit.org bots (probably hard) > - run the tests on our webkit canary bot (should be doable) > What do you think? > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
