On Wed, Sep 9, 2009 at 2:19 PM, Ojan Vafai <[email protected]> wrote:
> On Tue, Sep 8, 2009 at 6:43 PM, Jeremy Orlow <[email protected]> wrote: > >> On Wed, Sep 9, 2009 at 10:18 AM, Adam Barth <[email protected]> wrote: >> >>> > Or perhaps the >>> >> > Chromium port will just use JS bindings (no V8)? >>> >>> I think this is trickier than you might think. Also, it partially >>> defeats the point of upstreaming our port if we don't actually use the >>> upstream port. :) >>> >> >> Yes and no. It might be nice to have a Chromium+JSC and a Chromium+V8 >> bot. I know we (Dimitri, IIRC) were planning on doing this anyway on our >> own build infrastructure...why not do it upstream instead? >> > > If webkit folk are OK with us adding a bunch of builders (we'll want > Chromium mac/win/linux as well, right?), I think this is a great idea. > > >> > The lack of WebKit trybots is a real obstacle to landing large >>> patches/new >>> > files currently because I can't easily test the build-side changes on >>> the >>> > GTK and Qt ports, and it sounds like that issue will be exacerbated for >>> the >>> > Chromium port if we use the V8 bindings on the build bot. >>> >>> This is a large pain-point for a lot of WebKit contributors. bdash >>> has said that he's working on trybots, but they have yet to >>> materialize. I wonder if this is something we could help the WebKit >>> community with? >>> >> >> We can probably donate man-power, but I doubt they'll want to take any >> code from us (for whatever reason)...though we could always ask. :-) >> > > I've talked to bweinstein on #webkit about this. They are "blocked on > getting machines" and that is hoped to happen in a timeframe of "weeks, not > months". I don't know long it'll take to actually get them up once machines > arrive. > > I don't think it's just a question of manpower. And I don't know how we > could help them get machines faster. Maybe that's worth pursuing. > > This is easily my biggest painpoint with doing webkit development. If I > could just grab windows baselines off a trybot and not need to built/run > tests on Windows for WebKit, I honestly think I would be order of magnitude > more productive doing webkit patches. In fact, all I really want is a > Windows trybot (a Mac one wouldn't hurt). > > How hard would it be to just set these up ourselves on a chromium.org site > for our own use? (obviously we'd make it available to the broader WebKit > community) > I think Dimitri was telling me that you could use our try bot infastructure with WebKit patches even today. I've never tried it though. If it does work, we could definitely let them know it's an option for those who might want to. We'd have to phrase it delicately though. They're generally quite allergic to us even coming _close_ to pushing our infrastructure on them. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
