To clarify things; gcl upload automatically sends to the try server if you have access and makes sense. git cl doesn't.
Committers and Googlers have access to the google's try server. This server updates the code reviews try job status at http://codereview.chromium.org. It's relatively easy for a commiter to try a non-commiter patch. Just ask after uploading your patch. You can create your own server by following the instructions at http://dev.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source. You need at least 3 machines, one per OS. A master and a slave can cohabit on linux or mac but not on windows. http://dev.chromium.org/developers/testing is slightly stale since it's missing gmock and in-process browser tests. M-A On Mon, Jun 8, 2009 at 2:10 AM, Amanda Walker<[email protected]> wrote: > It does not depend on scope. By default, every change that is uploaded by a > committer for code review gets built on all three platforms by Google's try > servers. > --Amanda > > 2009/6/7 PhistucK <[email protected]> >> >> I forgot about the cross platform compiling stuff. >> I do not think every change is going through the try bot first, but only >> stuff that has greater scopes. >> About the testing thing, it says there "Here is a list of some of the >> tests currently used by Chromium:", so those are only some of them. >> ☆PhistucK >> >> >> 2009/6/8 <[email protected]> >>> >>> >A Try Bot is a machine that gets sent code patches and instantly (or not >>> > instantly) builds chrome with these changes >with the latest source. That >>> > is >>> > the place to see if the things you want to commit are fine, I guess mostly >>> > big, could->be-breaking changes are getting sent there. >>> >>> >Of course, only Chrome developers (Googlers) and contributors that can >>> > commit, can use the try bots. >>> >>> >>> >>> The TryBot is cool. >>> >>> Does that mean Googlers first submit theirs codes to trybots to test if >>> all the codes are OK, if OK, then they submit their codes to buildbots for >>> the final automated building and testing ? >>> >>> >>> >>> >>> >>> > 2009/6/7 nakro <[email protected]> >>> >>> >Regarding 1 : >>> >at least for VS2008 the tests seemed to have been moved to the chrome >>> >folder >>> >(i know that ui_tests.vcproj and unit_tests.vcproj have been moved >>> >there) >>> >>> >>> >>> well, nakro, that's the problem. I use vs2005, and I found 42 projects >>> under "Test". But at " http://dev.chromium.org/developers/testing";, there're >>> only 22 projects listed. What about the other 20 projects. >>> >>> >>> >>> I want to learn something from chromium's testing, for I think it really >>> organized well for a big project. >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
