How hard would it be to just make it configurable? On Wed, Sep 2, 2009 at 10:19 AM, David Levin <[email protected]> wrote:
> But the canaries are release so having debug for the try bots allows one to > find issues that the canaries don't catch with new webkit merges. > > On Tue, Sep 1, 2009 at 4:39 PM, Jeremy Orlow <[email protected]> wrote: > >> I'd suggest putting the webkit layout test slaves under release. This >> would allow us to catch debug/release build errors (since the normal bots >> are on debug) and layout tests run MUCH faster under release. >> >> >> On Tue, Sep 1, 2009 at 8:47 AM, Marc-Antoine Ruel <[email protected]>wrote: >> >>> >>> All try slaves are currently in debug. >>> >>> On Mon, Aug 31, 2009 at 4:15 PM, Julie Parent<[email protected]> >>> wrote: >>> > Are these running release or dbg? >>> > >>> > On Mon, Aug 31, 2009 at 1:12 PM, Marc-Antoine Ruel < >>> [email protected]> >>> > wrote: >>> >> >>> >> On Mon, Aug 31, 2009 at 12:39 PM, Brett Wilson<[email protected]> >>> wrote: >>> >> > On Mon, Aug 31, 2009 at 10:13 AM, Marc-Antoine Ruel< >>> [email protected]> >>> >> > wrote: >>> >> >> >>> >> >> If you are not a committer, you can skip this message. >>> >> >> >>> >> >> If you want to run layout tests as a try job, you can use the >>> layout >>> >> >> try slaves. They are not in the default pool so you need to >>> reference >>> >> >> them manually. >>> >> >> >>> >> >> The format is: >>> >> >> gcl try foo --bot layout_win,layout_mac,layout_linux >>> >> > >>> >> > This is great. Is this documented anywhere? Seems like >>> >> > http://dev.chromium.org/developers/how-tos/webkit-merge-1 would be >>> a >>> >> > very useful place to have it. >>> >> >>> >> I'm not a webkit gardener so I don't think I'm the best person to >>> >> modify this page with useful information. >>> >> >>> >> M-A >>> >> >>> >> >> >>> > >>> > >>> >>> >>> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
