3235a27e7a939c18cd57bbd7af6f818a7c8b9155 |
|
12-Jan-2016 |
Henrik Boström <hbos@webrtc.org> |
Updated chromium/.gclient and sync_chromium.py to not ignore third_party/ffmpeg. Was forgotten in this CL: https://codereview.webrtc.org/1575913003/ BUG=468365 R=kjellander@webrtc.org Review URL: https://codereview.webrtc.org/1579153003 . Cr-Commit-Position: refs/heads/master@{#11222}
/external/webrtc/sync_chromium.py
|
a9a1d2acaf71281a6f09cd85acb6bc21b02e5ce4 |
|
11-Jan-2016 |
hbos <hbos@webrtc.org> |
H.264: Default flags and pulling in openh264 and ffmpeg. Defining use_third_party_h264 directly, and indirectly defining use_openh264 (from third_party/openh264) and ffmpeg_branding (from third_party/ffmpeg). These will be used in a follow-up CL that adds an encoder and decoder implementation. The flags are added in this CL so that they can be used by trybots/waterfall bots in GN without "Build argument had no effect" errors. Equivalent GYP changes are also added. BUG=468365 Review URL: https://codereview.webrtc.org/1575913003 Cr-Commit-Position: refs/heads/master@{#11204}
/external/webrtc/sync_chromium.py
|
05ce5dd0f159c43b50bd87f7faf1fbe8f31d5845 |
|
15-Jun-2015 |
Henrik Kjellander <kjellander@webrtc.org> |
Roll chromium_revision e937e5f..c2239a8 (333350:334133) Removed no longer used test_isolation_outdir variable as in https://codereview.chromium.org/1176463003 The move of a DEPS in https://codereview.chromium.org/1155743013 is causing problems on some trybots. It shouldn't affect developers. Relevant changes: * src/third_party/android_tools: a3afc68..ed3dde6 * src/third_party/icu: 9939a5d..a05f412 * src/third_party/libjpeg_turbo: 8ee9bdd..f4631b6 * src/third_party/libyuv: 632c50f..632c50f Details: https://chromium.googlesource.com/chromium/src/+/e937e5f..c2239a8/DEPS Clang version was not updated in this roll. BUG= R=pbos@webrtc.org Review URL: https://codereview.webrtc.org/1182043002. Cr-Commit-Position: refs/heads/master@{#9435}
/external/webrtc/sync_chromium.py
|
10ba3eec5a268d359260e331fcc2608f818d5236 |
|
29-Apr-2015 |
Henrik Kjellander <kjellander@webrtc.org> |
Roll chromium_revision a12e1e1..0cb2549 (326495:327252) https://codereview.chromium.org/1051343002 adds a dependency on Chromium's third_party/junit into base/ which affects our Android tests that uses that code. The precompiled JUnit 4.11 JAR file that is only by the libjingle_peerconnection_java_unittest target on Linux has been moved to third_party/junit-jar, since it collided with the expected path for the JUnit dependency mentioned above. It had to be kept since the Chromium JUnit is only possible to build when OS==android. This CL also brings in Mockito and Robolectric, which should be useful for our Android tests. Other relevant changes: * src/buildtools: 3b302fe..15308f4 * src/third_party/libjpeg_turbo: 034e9a9..9e9058b * src/third_party/libyuv: 32ad6e0..01db3d1 Details: https://chromium.googlesource.com/chromium/src/+/a12e1e1..0cb2549/DEPS Clang version was not updated in this roll. BUG=4499 R=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/48239004 Cr-Commit-Position: refs/heads/master@{#9113}
/external/webrtc/sync_chromium.py
|
ae331349c64c2307a2ff06f2d3e1baedefc57d75 |
|
28-Apr-2015 |
Henrik Kjellander <kjellander@webrtc.org> |
Always specify current OS when syncing Chromium. Recently, we've hit a rare case of a dependency being present only below 'unix' and not in the 'android' section of the DEPS file in Chromium (src/third_party/junit/src). This exposed a bug in our sync_chromium.py script, which is that when the --deps flag is passed to gclient sync, _only_ that platform is processed. That means our Android builders synced with --deps=android and thus only getting the Android deps, not the 'unix' ones (Linux). That behavior is different from a regular gclient sync, where both the current platform's DEPS and the one specified by appending a target_os variable into .gclient is used. Ensuring that we pass both the current platform and the optionally specified DEPS platform into our sync_chromium.py sync, gives us the same behavior as a regular sync for the special Chromium sync we use. TESTED= First: rm chromium/.last_sync_chromium Then I ran without this patch and with target_os = ["android"] in .gclient. Verified that --deps=android was passed. With this patch, I repeated the above and verified --deps=unix,android was passed. R=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/52379004 Cr-Commit-Position: refs/heads/master@{#9103}
/external/webrtc/sync_chromium.py
|
b3fc48b28fe9ed679f9a054a75f4bce193b77b2f |
|
27-Mar-2015 |
Henrik Kjellander <kjellander@webrtc.org> |
Update the notice about the slow Chromium sync. It's no longer valid to run 'git auto-svn' since we've moved over to Git. R=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/50489004 Cr-Commit-Position: refs/heads/master@{#8880}
/external/webrtc/sync_chromium.py
|
74304330df4ed276b78f0fcdc51bcf77222d08dc |
|
05-Mar-2015 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Print better information during Chromium sync. Many users are having problems with the initial sync. Let's print a bit more information and advice on how to recover from an aborted sync. R=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/42229004 Cr-Commit-Position: refs/heads/master@{#8617} git-svn-id: http://webrtc.googlecode.com/svn/trunk@8617 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
bfdee69d486e05af5bb9f3e4f68f6c79028eca9e |
|
03-Feb-2015 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Roll chromium_revision 9070a80..cd35af6 (313233:314322) Relevant changes: * src/third_party/boringssl/src: 347f025..be629e0 * src/third_party/libvpx: 5da40ca..5cdd302 * src/third_party/openmax_dl: 8f7bf0b..c01d587 * src/tools/gyp: b28bd7d..4d7c139 * src/tools/swarming_client: d863df3..c698ea2 Details: https://chromium.googlesource.com/chromium/src/+/9070a80..cd35af6/DEPS Clang version was not updated in this roll. webrtc_tests.py had to be updated to match changes in https://codereview.chromium.org/882713002 A workaround for grit resources and the addition of V8 to the Chromium checkout had to be done due to changed dependencies caused by https://codereview.chromium.org/867073002 R=pbos@webrtc.org Review URL: https://webrtc-codereview.appspot.com/35969004 Cr-Commit-Position: refs/heads/master@{#8234} git-svn-id: http://webrtc.googlecode.com/svn/trunk@8234 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
7d4e6d012c16bbe8b7958abf5341193afc1629e6 |
|
27-Nov-2014 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Roll chromium_revision d8c9041..309cf65 Relevant changes: * testing/gtest 4650552..8245545 * testing/gmock 896ba0e..2976396 * third_party/boringssl 2f3ba91..69a0160 * third_party/icu: 6242e2f..dd72764 * third_party/libyuv: 5a09c3e..d204db6 * tools/gyp: b13d8f2..0a381c0 Details: https://chromium.googlesource.com/chromium/src/+/d8c9041..309cf65/DEPS Clang version was not updated in this roll. R=pbos@webrtc.org Review URL: https://webrtc-codereview.appspot.com/25219004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7757 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
dde19a6f6033a26be67fa56a96a211d8ec4b9df8 |
|
24-Nov-2014 |
kjellander@webrtc.org <kjellander@webrtc.org> |
sync_chromium.py: Check for chromium/src Make sure the script alwyas downloads Chromium if there's no current download. This case can happen if a user is removing the 'src' folder but doesn't know to remove the .last_sync_chromium file. BUG= TESTED=Renamed chromium/src and ran a sync keeping the .last_sync_chromium file, verified it started downloading. TBR=iannucci@chromium.org Review URL: https://webrtc-codereview.appspot.com/27099004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7738 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
8539bd01849083e12a5cd12341834553356d2396 |
|
23-Oct-2014 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Download full Chromium checkouts by default This changes sync_chromium.py to download a full Chromium checkout instead of one with no history. It has been noticed that the download of the no-history checkout is very slow, even when on high-speed internet connections, due to current limitations in the Git backend serving these clones. Switching to a full checkout is faster, but requires more bandwidth and disk space. To keep the old behavior, users must set the CHROMIUM_NO_HISTORY environment variable to 1. Using a full checkout also enables the use of the Chromium infrastructure teams' Git cache functionality, that speeds up the initial download and also heavily reduces the traffic when setting up multiple checkouts on the same machine. This is not enabled by default, but is supported if the user is setting the cache_dir variable in his checkout's .gclient file to point at a directory on local disk. BUG=3882 TESTED= * Ran gclient sync and verified chromium/src now contained a Git repo with full history. * Tested rolling chromium_revision in DEPS forward + sync. * Tested rolling it back again + sync. * Tested with an existing no-history checkout: CHROMIUM_NO_HISTORY=1 gclient sync No change was performed. * Tested with a .gclient that had cache_dir configured. * Verified error message is displayed when .gclient has cache_dir configured and CHROMIUM_NO_HISTORY=1. R=iannucci@chromium.org Review URL: https://webrtc-codereview.appspot.com/22869004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7506 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
6c6680a9d439a446aa69792fd13a085427d09d55 |
|
27-Sep-2014 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Cleanup .gclient.bot_entries to avoid sync problems on bots. In https://webrtc-codereview.appspot.com/28509004 the buildbot case was missed since they get a gclient entries file named .gclient.bot_entries instead of the regular .gclient_entries file due to the way the sync was implemented for buildbots. This change makes the right file get wiped in the two cases. BUG= TBR=agable@chromium.org Review URL: https://webrtc-codereview.appspot.com/28599004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7314 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
e94f83a1919120deb48e97bc91955d0ca12e43fe |
|
18-Sep-2014 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Cleanup .gclient_entries to avoid sync problems. The .gclient_entries file is written after a successful gclient sync operation and contains paths mapped to URLs for all DEPS entries that have been synced. This has been causing problems for users when switching from the legacy Subversion based checkouts to the new DEPS approach using a Chromium Git checkout combined with symlinks. Also it has been discovered that when entries have been removed from the Chromium DEPS file, subsequent gclient sync operations fail when it's trying to process those directories. This CL changes so that .gclient_entries is wiped for the WebRTC checkout when moving from the legacy SVN to Git. It also wipes the chromium/.gclient_entries file when a new Chromium revision is about to be synced, to avoid problems when DEPS entries have been removed. BUG=415219 R=agable@chromium.org Review URL: https://webrtc-codereview.appspot.com/28509004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7222 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
dc926a000e1c8054b1d5e0a79431963731f37f1c |
|
26-Aug-2014 |
kjellander@webrtc.org <kjellander@webrtc.org> |
Avoid syncing unnecessary Chromium deps for WebRTC. This should save several gigabytes of traffic and disk space. On Linux this is about 2.6 GB: 346M src/chrome/tools/test/reference_build 340M src/native_client 170M src/third_party/ffmpeg 1.5G src/third_party/WebKit 196M src/v8 BUG=2863 TESTED=Removed the directories locally, ran a sync and verified they didn't reappear (or fail because of platform-specific ones). R=iannucci@chromium.org, niklas.enbom@webrtc.org Review URL: https://webrtc-codereview.appspot.com/22189004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6984 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
374d39b7aed15aaa7bbf0a66cfd4f22ad6281fab |
|
21-Aug-2014 |
kjellander@webrtc.org <kjellander@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Increment sync_chromium.py version to force re-sync This should make the remaining red Windows bots cycle green. Currently, some of them are in a bad state for the Chromium checkout. BUG=webrtc:2863 TBR=niklas.enbom@webrtc.org Review URL: https://webrtc-codereview.appspot.com/18229004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6953 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
161363808b850762fe48f32bb6482a351d0e79e7 |
|
21-Aug-2014 |
iannucci@chromium.org <iannucci@chromium.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Make the last_sync_chromium file a bit more comprehensive. Adds a SCRIPT_VERSION and the target_os_list to the flag file content. The script version is so that we can arbitrarially make all slaves/devs re-sync (in case we change the implementation but don't want to roll chromium), and the target_os_list is so that devs who change the target_os_list in their .gclient file don't mysteriously fail to get the new deps. R=kjellander@webrtc.org, agable@chromium.org, szager@chromium.org BUG=2863, chromium:339647 Review URL: https://webrtc-codereview.appspot.com/17189004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6952 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
286210d3ec6e49558434cc197d24348300893d92 |
|
21-Aug-2014 |
iannucci@chromium.org <iannucci@chromium.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Use --gclientfile instead of --spec, because windows is THE WORST. --spec contains newlines, which are interpreted as actual newlines in the command line, which causes gclient to fall apart at the seams. TBR=agable@chromium.org, kjellander@webrtc.org, szager@chromium.org BUG=2863, chromium:339647 Review URL: https://webrtc-codereview.appspot.com/22429004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6944 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
98d92d63e2af073d4703c9a6333162a8d7a083e2 |
|
21-Aug-2014 |
iannucci@chromium.org <iannucci@chromium.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Make sync_chromium use the git-cache when on the bots. This should help bootstrapping speed, as well as allow better clobbering support. R=agable@chromium.org TBR=agable@chromium.org, kjellander@webrtc.org, szager@chromium.org BUG=2863, chromium:339647 Review URL: https://webrtc-codereview.appspot.com/17179004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6943 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
3aa837ca28a9f4482ec001c1b748140184ad5930 |
|
20-Aug-2014 |
kjellander@webrtc.org <kjellander@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Increase verbosity for gclient sync of Chromium In r6939 the --verbose flag was passed to the problematic (approx 2.2GB large) gclient sync of Chromium's src.git repo. However the bots are still hitting killed sync jobs due to lack of output. This is a speculative attempt to provoke even more logging, in order to trigger buffer flushing for the buildbot execution. BUG=2863, chromium:339647 TEST=Ran gclient runhooks locally with CHROME_HEADLESS=1 set. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/21269004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6940 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
bbca4dde0cd3755f97f0d00f0330b0469a88c4da |
|
20-Aug-2014 |
kjellander@webrtc.org <kjellander@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Pass --verbose to gclient sync of Chromium In r6938 the switch to using Chromium's Git repo was deployed. However this fails on the bots since their timeout for steps without output is 1200 seconds, which is not enough to checkout the large Chromium Git repo. Adding --verbose will print more output, thus getting a longer timeout that should be enough for the runhooks step to complete. BUG=2863, chromium:339647 TEST=None TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/15209004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6939 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|
8925662318ca10d841e92f4dc20bbf0c53aea865 |
|
20-Aug-2014 |
kjellander@webrtc.org <kjellander@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Make WebRTC work with Chromium Git checkouts WebRTC standalone shares a lot of dependencies and build tools with Chromium. To make the build work, many of the paths of a Chromium checkout is now emulated by creating symlinks to files and directories. All DEPS entries that previously used Var("chromium_trunk") to reference a Chromium checkout or From("chromium_deps"..) to reference the Chromium DEPS file are now removed and replaced by symlink entries in setup_links.py. The script also handles cleanup of the legacy Subversion-based dependencies that's needed for the transition. Windows: One Windows-specific important change is that gclient sync|runhooks must now be run from a shell with Administrator privileges in order to be able to create symlinks. This also means that Windows XP is no longer supported. To transition a previously created checkout: Run "python setup_links.py --force" to cleanup the old SVN-based dependencies that have been synced by gclient sync. For Buildbots, the --force flag is automatically enabled for their syncs. BUG=2863, chromium:339647 TEST=Manual testing on Linux, Mac and Windows. R=andrew@webrtc.org, iannucci@chromium.org, phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/18379005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6938 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/sync_chromium.py
|