- 03 Dec, 2018 14 commits
-
-
Sam McNally authored
- Remove testPromise and StepsRunner. - Assume all files app integration tests return a promise. - Change helpers in background.js to use async-await. - Change setupAndWaitUntilReady to only return the app ID and to not take a callback. Bug: 909056 Change-Id: I5a2f9c87665ab39b8c814f67332b100dea1e32dc Reviewed-on: https://chromium-review.googlesource.com/c/1356738 Commit-Queue: Sam McNally <sammc@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#613000}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/61ea30737c65..0b287c5bcafd git log 61ea30737c65..0b287c5bcafd --date=short --no-merges --format='%ad %ae %s' 2018-12-03 tikuta@chromium.org introduce ninjalog_uploader to autoninja.bat Created with: gclient setdep -r src/third_party/depot_tools@0b287c5bcafd The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:900161 TBR=agable@chromium.org Change-Id: Ie0f08417833db7f8f632808c1513638f104da034 Reviewed-on: https://chromium-review.googlesource.com/c/1358081Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#612999}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: Ib9af0ff0386cbcfd4dd21ac9b33f50da0a8be2f6 Reviewed-on: https://chromium-review.googlesource.com/c/1357905Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#612998}
-
Noel Gordon authored
- remove media_inport_handler_unittest.html - add BUILD rules to auto-generate and compile this unittest - define mockChrome, install it during the unittest - remove unused unittest vars and JS auto-format - document test fixtures and test helpers - fix Closure compile errors (there were lots). No change in test behavior, no new tests. Bug: 907970 Change-Id: Id90b4b1eaf84764521fb0d77aa2c29ff56db7c07 Reviewed-on: https://chromium-review.googlesource.com/c/1356728 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
-
Hirokazu Honda authored
This reverts commit f0e7045f. Reason for revert: Power regression on eve crbug.com/910986 Original change's description: > Vaapi: Activate |decode_using_client_picture_buffers_| for h264 > > This CL cleans up and activates |decode_using_client_picture_buffers_| > after recent power consumption measurements done by the Intel folks > reveal that there should be no regression, and also because skipping > the Vpp has a huge impact in memory consumption since Va doesn't need > to allocate ~13/14 Buffer Objects inside (see crbug.com/909926). > > Bug: 909926, 822346 > Change-Id: Ie8d6b41521f5d8ee62568f9674ae071a67c290bf > Reviewed-on: https://chromium-review.googlesource.com/c/1356019 > Reviewed-by: Hirokazu Honda <hiroh@chromium.org> > Commit-Queue: Miguel Casas <mcasas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612498} TBR=mcasas@chromium.org,hiroh@chromium.org,sreerenj.balachandran@intel.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 909926, 822346 910986 Change-Id: I1cb5d54064413d27cd3472e9918c5fcd62385a1c Reviewed-on: https://chromium-review.googlesource.com/c/1358099Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#612996}
-
Joshua Peraza authored
mini_chromium and Crashpad's zlib are checked out directly with Crashpad, so don't have their own README.chromium. They are only used when building Crashpad outside chromium. No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I9298c8071dafef84e85992ade91c3801757588f3 Reviewed-on: https://chromium-review.googlesource.com/c/1358002 Commit-Queue: calamity <calamity@chromium.org> Reviewed-by:
Hiroshi Ichikawa <ichikawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#612995}
-
Sam McNally authored
Bug: 819822 Change-Id: I1900ba4bf4c3a1e3c2f407b1fb45f883b0ff5d25 Reviewed-on: https://chromium-review.googlesource.com/c/1263677Reviewed-by:
-
Matt Falkenhagen authored
Change-Id: I5b4035dadf55b3a5e1d1b32010f0bfd324ad9b6b Reviewed-on: https://chromium-review.googlesource.com/c/1355313Reviewed-by:
agrieve <agrieve@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#612993}
-
Chris Hall authored
R=dmazzoni,aboxhall BUG=889370 Change-Id: Ic3cb08d971a387fe55fe9b6c527eaab09db18dd5 Reviewed-on: https://chromium-review.googlesource.com/c/1354734 Commit-Queue: Chris Hall <chrishall@chromium.org> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#612992}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/53a14f8c058b..897e391e1f64 Created with: gclient setdep -r src-internal@897e391e1f64 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: Id885b19ffdd455527b821d7c5999ca8fc344c231 Reviewed-on: https://chromium-review.googlesource.com/c/1358080Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#612991}
-
Noel Gordon authored
- remove file_operation_handler_unittest.html - add BUILD rules to auto-generate and compile this unittest - document, add Closure @type's, and auto-format the unittest - fix Closure compile errors No change in test behavior, no new tests. Bug: 910774 Change-Id: Ie91e8ac6951821af05cd5c8482b7be7ae2c3b04f Reviewed-on: https://chromium-review.googlesource.com/c/1356726 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
-
calamity authored
This reverts commit 66b2e0f1. Reason for revert: Breaks compile https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/android-rel/5134 Original change's description: > Enable Crashpad for Android > > Overview: > This CL disables Breakpad for Chrome, Content Shell, WebView, and > Chromecast on Android and replaces it with Crashpad. When a crash > signal is received, the browser forks+execs a Crashpad handler process > either for itself or on behalf of a crashing child to create a crash > dump. > > components/crash/ > - Remove CrashDumpManager. Minidump creation is handled entirely by > Crashpad. > - Remove OnChildStart from ChildExitObserver as it is no longer > necessary. > - ChildExitObserver observers CrashHandlerHost to be notified when > child processes receive crash signals. > - De-duplicate calls to ChildExitObserver::Client::OnChildExit when > NOTIFICATION_RENDER_PROCESS_{CLOSED, TERMINATED} are both sent. > > components/minidump_uploader/ > - Uploaders expect crash reports to already be MIME encoded since > Breakpad was doing that in a signal handler call-back. > CrashFileManager now automatically calls into native code to do > the encoding and write to a directory of crash reports whenever it > checks for reports without logcats. > > chrome/app/*.{cc,h} > chrome/browser/*.cc > content/shell/app/*.{cc,h} > content/shell/browser/*.cc > - Initialize Crashpad instead of Breakpad, with minor cleanup and > adjustment for changes to CrashDumpObserver. > > chrome/browser/metrics/oom/out_of_memory_reporter_unittest.cc > - Simulate crashes/exits with NOTIFICATION_RENDER_PROCESS_{CREATED, > CLOSED} and signals sent to ChildExitObserver instead of a crash > dump. > > android_webview/ > - AwBrowserTerminator now observes child process crashes via > ChildExitObserver rather than its own pipe. > - Crashpad always produces minidumps, and not microdumps. > - Disabling Crashpad is not yet supported. > > chromecast/ > - There are now two directories that crash report uploaders should > be aware of: "Crashpad" contains a database of raw minidumps > produced by Crashpad, and "Crash Reports" contains MIME encoded > minidumps. MIME encoding is performed by a CrashReportMimeWriter > in CastCrashUploader.java:checkForCrashDumps(). > > Bug: crashpad:30 > Cq-Include-Trybots: master.tryserver.chromium.android:android_compile_x64_dbg;master.tryserver.chromium.android:android_compile_x86_dbg > Change-Id: I0efa451585f60287853c47f860f09ced581c8958 > Reviewed-on: https://chromium-review.googlesource.com/c/989401 > Commit-Queue: Joshua Peraza <jperaza@chromium.org> > Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org> > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > Reviewed-by: Peter Wen <wnwen@chromium.org> > Reviewed-by: Luke Halliwell <halliwell@chromium.org> > Reviewed-by: Simeon Anfinrud <sanfin@chromium.org> > Reviewed-by: Yaron Friedman <yfriedman@chromium.org> > Reviewed-by: Mark Mentovai <mark@chromium.org> > Reviewed-by: Peter Beverloo <peter@chromium.org> > Reviewed-by: Ilya Sherman <isherman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612987} TBR=yfriedman@chromium.org,peter@chromium.org,isherman@chromium.org,jam@chromium.org,wnwen@chromium.org,torne@chromium.org,halliwell@chromium.org,tobiasjs@chromium.org,rsesek@chromium.org,sanfin@chromium.org,jperaza@chromium.org,mark@chromium.org Change-Id: I602251d05a6f89aa8f1a7c40c50d7b413fb514d4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: crashpad:30 Cq-Include-Trybots: master.tryserver.chromium.android:android_compile_x64_dbg;master.tryserver.chromium.android:android_compile_x86_dbg Reviewed-on: https://chromium-review.googlesource.com/c/1358103Reviewed-by:
calamity <calamity@chromium.org> Commit-Queue: calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#612989}
-
Noel Gordon authored
- banners.js depends on type {chrome.echoPrivate} - add externs deps: externs/chrome_echo_private.js - combobutton.js and files_menu.js depend on type {PaperRipple} - add externs deps: externs/paper_elements.js - providers_menu.js depends on type {MenuItemUpdateEvent} - add externs deps: externs/menu_item_update_event.js - search_box.js depends on type {SearchItem} - add externs deps: externs/search_item.js - suggest_apps_dialog.js depends on {chrome.webstoreWidgetPrivate} - add externs deps: externs/chrome_webstore_widget_private.js No change in test behavior, no new tests. Bug: 910975 Change-Id: Ib38947f6f6717b9767be6ec4472b1bbd16ac384a Reviewed-on: https://chromium-review.googlesource.com/c/1356734Reviewed-by: -
Joshua Peraza authored
Overview: This CL disables Breakpad for Chrome, Content Shell, WebView, and Chromecast on Android and replaces it with Crashpad. When a crash signal is received, the browser forks+execs a Crashpad handler process either for itself or on behalf of a crashing child to create a crash dump. components/crash/ - Remove CrashDumpManager. Minidump creation is handled entirely by Crashpad. - Remove OnChildStart from ChildExitObserver as it is no longer necessary. - ChildExitObserver observers CrashHandlerHost to be notified when child processes receive crash signals. - De-duplicate calls to ChildExitObserver::Client::OnChildExit when NOTIFICATION_RENDER_PROCESS_{CLOSED, TERMINATED} are both sent. components/minidump_uploader/ - Uploaders expect crash reports to already be MIME encoded since Breakpad was doing that in a signal handler call-back. CrashFileManager now automatically calls into native code to do the encoding and write to a directory of crash reports whenever it checks for reports without logcats. chrome/app/*.{cc,h} chrome/browser/*.cc content/shell/app/*.{cc,h} content/shell/browser/*.cc - Initialize Crashpad instead of Breakpad, with minor cleanup and adjustment for changes to CrashDumpObserver. chrome/browser/metrics/oom/out_of_memory_reporter_unittest.cc - Simulate crashes/exits with NOTIFICATION_RENDER_PROCESS_{CREATED, CLOSED} and signals sent to ChildExitObserver instead of a crash dump. android_webview/ - AwBrowserTerminator now observes child process crashes via ChildExitObserver rather than its own pipe. - Crashpad always produces minidumps, and not microdumps. - Disabling Crashpad is not yet supported. chromecast/ - There are now two directories that crash report uploaders should be aware of: "Crashpad" contains a database of raw minidumps produced by Crashpad, and "Crash Reports" contains MIME encoded minidumps. MIME encoding is performed by a CrashReportMimeWriter in CastCrashUploader.java:checkForCrashDumps(). Bug: crashpad:30 Cq-Include-Trybots: master.tryserver.chromium.android:android_compile_x64_dbg;master.tryserver.chromium.android:android_compile_x86_dbg Change-Id: I0efa451585f60287853c47f860f09ced581c8958 Reviewed-on: https://chromium-review.googlesource.com/c/989401 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by:Tobias Sargeant <tobiasjs@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Peter Wen <wnwen@chromium.org> Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Reviewed-by:
Simeon Anfinrud <sanfin@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#612987}
-
- 02 Dec, 2018 26 commits
-
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ae58624a3a9b..53a14f8c058b Created with: gclient setdep -r src-internal@53a14f8c058b The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: Iaf777c3c5c941f895052e934544f181d20bd14f7 Reviewed-on: https://chromium-review.googlesource.com/c/1358079Reviewed-by:
-
dstockwell authored
Most of this change was automated by running `eslint --fix` but a few cases were resolved manually (in particular global definitions and typedefs). Bug: 792774 Change-Id: Iea4e373a088d7d276975bf946a738bc9d81772c3 Reviewed-on: https://chromium-review.googlesource.com/c/1355302 Commit-Queue: dstockwell <dstockwell@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#612985}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/dfda24364504..ae58624a3a9b Created with: gclient setdep -r src-internal@ae58624a3a9b The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: Ib268a116f56f6afa15dfa54a65a0e2e0389c416b Reviewed-on: https://chromium-review.googlesource.com/c/1357897Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1354d1a0ca50..dfda24364504 Created with: gclient setdep -r src-internal@dfda24364504 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: Idcc3f324ca52f1b4446ffe785a34e86a01ffbc6f Reviewed-on: https://chromium-review.googlesource.com/c/1357896Reviewed-by:
-
Findit authored
This reverts commit a61d2bb4. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 612980 as the culprit for flakes in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYTYxZDJiYjQzMDRkZjgyOGRhNjBhZjA3ZjBiMDVmMzNlNDlmZDE4Zgw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/9304 Sample Failed Step: sync_integration_tests Sample Flaky Test: SingleClientSessionsSyncTest.NavigateThenCloseTabThenOpenTab Original change's description: > Reland "Avoid recycling sync tabs if commit pending" > > This is a reland of 62414cfc > > Test improved to avoid flakes. > > Original change's description: > > Avoid recycling sync tabs if commit pending > > > > When a tab is closed, it's possible that the corresponding history > > hasn't been committed yet, and hence there is a risk that synced history > > is lost if the entity is recycled (for another tab that is opened). > > > > In this patch, and behind a feature toggle, this issue is prevented by > > *not* freeing tab nodes while the sync entity is unsynced. Old tabs are > > excluded from this (to avoid problems with expired history) and a max > > cap is also introduced to the number of tabs in this state, in order to > > avoid memory regressions. > > > > Bug: 882489 > > Change-Id: I6dd796642f9553f2713a0814731897a4ffb13f0b > > Reviewed-on: https://chromium-review.googlesource.com/c/1356541 > > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > > Reviewed-by: Marc Treib <treib@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#612971} > > TBR=treib@chromium.org > > Bug: 882489 > Change-Id: Ib3f3ff9e4d620512435d9b22ba7b2c338f92203f > Reviewed-on: https://chromium-review.googlesource.com/c/1357086 > Reviewed-by: Mikel Astiz <mastiz@chromium.org> > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612980} Change-Id: I69bf304dc196b29f2b6ccf5f15ff8dd77ca7d610 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 882489, 910947 Reviewed-on: https://chromium-review.googlesource.com/c/1357826 Cr-Commit-Position: refs/heads/master@{#612982}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d33123b9f809..1354d1a0ca50 Created with: gclient setdep -r src-internal@1354d1a0ca50 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I58962cea7d1ca7bd32a27ca09b215b6e1514760e Reviewed-on: https://chromium-review.googlesource.com/c/1357895Reviewed-by:
-
Mikel Astiz authored
This is a reland of 62414cfc Test improved to avoid flakes. Original change's description: > Avoid recycling sync tabs if commit pending > > When a tab is closed, it's possible that the corresponding history > hasn't been committed yet, and hence there is a risk that synced history > is lost if the entity is recycled (for another tab that is opened). > > In this patch, and behind a feature toggle, this issue is prevented by > *not* freeing tab nodes while the sync entity is unsynced. Old tabs are > excluded from this (to avoid problems with expired history) and a max > cap is also introduced to the number of tabs in this state, in order to > avoid memory regressions. > > Bug: 882489 > Change-Id: I6dd796642f9553f2713a0814731897a4ffb13f0b > Reviewed-on: https://chromium-review.googlesource.com/c/1356541 > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > Reviewed-by: Marc Treib <treib@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612971} TBR=treib@chromium.org Bug: 882489 Change-Id: Ib3f3ff9e4d620512435d9b22ba7b2c338f92203f Reviewed-on: https://chromium-review.googlesource.com/c/1357086Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#612980}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/affb25a9e181..d33123b9f809 Created with: gclient setdep -r src-internal@d33123b9f809 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I46761826d6c9bf0a748dad070bc253b35ea5bebb Reviewed-on: https://chromium-review.googlesource.com/c/1357894Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/565bc6695ef2..affb25a9e181 Created with: gclient setdep -r src-internal@affb25a9e181 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I0e3bdea97fa4e1e7267c0dcfe4c253918e29f54e Reviewed-on: https://chromium-review.googlesource.com/c/1357893Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/0cc11b4b947e..21d8b181f663 git log 0cc11b4b947e..21d8b181f663 --date=short --no-merges --format='%ad %ae %s' 2018-12-02 kwiberg@webrtc.org Remove some unused forward declarations 2018-12-01 zstein@webrtc.org Add transaction id to candidate pair event log parser and encoder. 2018-12-01 zstein@webrtc.org Log DTLS writable changes to RtcEventLog 2018-12-01 benwright@webrtc.org Add BufferedFrameDecryptor to cleanly deal with receiving encrypted frames. 2018-12-01 qingsi@webrtc.org Revert "Fix output period in RtcEventLogImpl" 2018-11-30 magjed@webrtc.org Android: Add constant for native EGL NO_CONTEXT 2018-11-30 zstein@webrtc.org Reland "Add transaction id to CandidatePairEvents." 2018-11-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 173a384b..3546854f (612554:612694) 2018-11-30 ouj@fb.com Parse `ice_unwritable_timeout` and `ice_unwritable_min_checks` from RTCConfiguration into IceConfig 2018-11-30 steveanton@webrtc.org Add integration test for new GetStats() with many tracks 2018-11-30 eladalon@webrtc.org Fix output period in RtcEventLogImpl 2018-11-30 sprang@webrtc.org Remove deprecated VideoEncoder metadata methods 2018-11-30 mirtad@webrtc.org Add metadata from VideoEncoderFactory::CodecInfo to VideoEncoder::EncoderInfo 2018-11-30 nisse@webrtc.org Move implementation of LoopbackMediaTransport to .cc file 2018-11-30 srte@webrtc.org Fixes DCHECK bug in LinkCapacityEstimator. 2018-11-30 srte@webrtc.org Friendlier error messages from data unit classes. 2018-11-30 sprang@webrtc.org Revert "Add transaction id to CandidatePairEvents." 2018-11-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 77dd2659..173a384b (612445:612554) 2018-11-30 braveyao@webrtc.org desktop_capture: apply scale to cursor relative positon on Mac only 2018-11-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision d6514607..77dd2659 (612330:612445) 2018-11-29 zstein@webrtc.org Add transaction id to CandidatePairEvents. 2018-11-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0a7ee900..d6514607 (612216:612330) 2018-11-29 srte@webrtc.org Extracts LinkCapacityEstimator from AimdRateControl. 2018-11-29 sprang@webrtc.org Cap probing bitrate to max total allocated bitrate 2018-11-29 crodbro@webrtc.org Unittests for loss based bandwidth estimation. 2018-11-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision f85d2e4d..0a7ee900 (612092:612216) 2018-11-29 phoglund@webrtc.org Revert "Various VP9 high fps fixes" 2018-11-29 phoglund@webrtc.org Try UWP with msvc. 2018-11-29 sprang@webrtc.org Make simulcast screenshare default-on 2018-11-29 nisse@webrtc.org Delete method EncodedFrame::GetBitstream, part 2 2018-11-29 nisse@webrtc.org Move size() method to EncodedImage base class 2018-11-29 phoglund@webrtc.org Disable goma for uwp bots. 2018-11-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 2f5059a4..f85d2e4d (611832:612092) 2018-11-29 phoglund@webrtc.org Add Win UWP bots. 2018-11-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 28d61688..2f5059a4 (611644:611832) 2018-11-28 steveanton@webrtc.org [Unified Plan] Fix old GetStats() not associating track id 2018-11-28 zstein@webrtc.org Log DTLS state changes to RtcEventLog 2018-11-28 hta@webrtc.org Add API for returning a webrtc::DtlsTransport for a MID on a PC 2018-11-28 yvesg@webrtc.org [Cleanup] Add missing #include. Remove useless ones. IWYU part 2. 2018-11-28 oprypin@webrtc.org Add new names of perf bots that will be migrated to LUCI 2018-11-28 ssilkin@webrtc.org Keep bitrate constraints. 2018-11-28 artit@webrtc.org Reland "Run robolectric tests for Android on several Android API versions" 2018-11-28 nisse@webrtc.org Add video support to LoopbackMediaTransport 2018-11-28 nisse@webrtc.org Delete ssrc book-keeping in NetEq 2018-11-28 andersc@webrtc.org React to changes in either width or height in iOS Metal renderer. 2018-11-28 sakal@webrtc.org Add missing files to AAR. 2018-11-28 nisse@webrtc.org Delete method EncodedFrame::GetBitstream, part 1 Created with: gclient setdep -r src/third_party/webrtc@21d8b181f663 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng BUG=chromium:None,chromium:None,chromium:None,chromium:None,chromium:909784,chromium:None,chromium:None,chromium:none,chromium:None,chromium:690537,chromium:None,chromium:None,chromium:906988,chromium:907849,chromium:908001 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ia2a0ebb98aeece46ef99b2c5f9e622f088ba3822 Reviewed-on: https://chromium-review.googlesource.com/c/1357892Reviewed-by:
-
Findit authored
This reverts commit 62414cfc. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 612971 as the culprit for flakes in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vNjI0MTRjZmNkZThiNzA0NTk5ODQ3ZDZhY2M3MzFkMjU0NDc5NjU1Zgw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.mac/Mac10.11%20Tests/31315 Sample Failed Step: sync_integration_tests on (none) GPU on Mac on Mac-10.11 Sample Flaky Test: SingleClientSessionsSyncTest.NavigateThenCloseTabThenOpenTab Original change's description: > Avoid recycling sync tabs if commit pending > > When a tab is closed, it's possible that the corresponding history > hasn't been committed yet, and hence there is a risk that synced history > is lost if the entity is recycled (for another tab that is opened). > > In this patch, and behind a feature toggle, this issue is prevented by > *not* freeing tab nodes while the sync entity is unsynced. Old tabs are > excluded from this (to avoid problems with expired history) and a max > cap is also introduced to the number of tabs in this state, in order to > avoid memory regressions. > > Bug: 882489 > Change-Id: I6dd796642f9553f2713a0814731897a4ffb13f0b > Reviewed-on: https://chromium-review.googlesource.com/c/1356541 > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > Reviewed-by: Marc Treib <treib@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612971} Change-Id: I7735b817751abcbd18bded6a731115333ee50b26 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 882489, 910947 Reviewed-on: https://chromium-review.googlesource.com/c/1357999 Cr-Commit-Position: refs/heads/master@{#612976}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/baba3f8b15c5..565bc6695ef2 Created with: gclient setdep -r src-internal@565bc6695ef2 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I0ad2a56fea1a565c23057f43eea4627b1b43e6b2 Reviewed-on: https://chromium-review.googlesource.com/c/1357891Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b6d4fb5081ba..baba3f8b15c5 Created with: gclient setdep -r src-internal@baba3f8b15c5 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I1c4d1798c941dfaa21a2c690ca7937ec2d48c8fa Reviewed-on: https://chromium-review.googlesource.com/c/1357890Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/d5cded1697ed..58dc4bf4fc2b git log d5cded1697ed..58dc4bf4fc2b --date=short --no-merges --format='%ad %ae %s' 2018-12-02 garryxiao@chromium.org group_baseline: add group suzy-q Created with: gclient setdep -r src/third_party/chromite@58dc4bf4fc2b The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=chrome-os-gardeners@chromium.org Change-Id: I352aa8e5d7c44279b132955585f0573eb160e920 Reviewed-on: https://chromium-review.googlesource.com/c/1357889Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c8b231e26255..b6d4fb5081ba Created with: gclient setdep -r src-internal@b6d4fb5081ba The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: Ifbec2721c4c1559eb9f3acaca9ae3264593e780b Reviewed-on: https://chromium-review.googlesource.com/c/1357888Reviewed-by:
-
Mikel Astiz authored
When a tab is closed, it's possible that the corresponding history hasn't been committed yet, and hence there is a risk that synced history is lost if the entity is recycled (for another tab that is opened). In this patch, and behind a feature toggle, this issue is prevented by *not* freeing tab nodes while the sync entity is unsynced. Old tabs are excluded from this (to avoid problems with expired history) and a max cap is also introduced to the number of tabs in this state, in order to avoid memory regressions. Bug: 882489 Change-Id: I6dd796642f9553f2713a0814731897a4ffb13f0b Reviewed-on: https://chromium-review.googlesource.com/c/1356541 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#612971}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/86ff2e751864..c8b231e26255 Created with: gclient setdep -r src-internal@c8b231e26255 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I991cebf66786d1f49a828e90fb54b4c402de9068 Reviewed-on: https://chromium-review.googlesource.com/c/1357886Reviewed-by:
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=gbiv@chromium.org Change-Id: I72fdde7e958faeebc986bbfe0b9107bdf1240bb0 Reviewed-on: https://chromium-review.googlesource.com/c/1357920Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2ec7409514ed..86ff2e751864 Created with: gclient setdep -r src-internal@86ff2e751864 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I39c6c6338c435945d321ea0c431f08068debf630 Reviewed-on: https://chromium-review.googlesource.com/c/1357884Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/248876f7b6b1..2ec7409514ed Created with: gclient setdep -r src-internal@2ec7409514ed The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I6745961f09d6d366b59d52eaa8b519de70d2551a Reviewed-on: https://chromium-review.googlesource.com/c/1357882Reviewed-by:
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Icbb5afb6b21e64e5717717b68182e4480f45be5e Reviewed-on: https://chromium-review.googlesource.com/c/1357880Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4bc9893eed87..248876f7b6b1 Created with: gclient setdep -r src-internal@248876f7b6b1 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I0d0cd5441f42a6df4e3f136594cf29a2000e29b4 Reviewed-on: https://chromium-review.googlesource.com/c/1357881Reviewed-by:
-
Victor Costan authored
This CL aligns the process for changing SQLite with the new process for upgrading SQLite. Change-Id: I0bfd95855606642de569844145b1d4b0117341c4 Reviewed-on: https://chromium-review.googlesource.com/c/1349458 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Chris Mumford <cmumford@chromium.org> Cr-Commit-Position: refs/heads/master@{#612964}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: Id31f83702db71aece936782e49233448184a486a Reviewed-on: https://chromium-review.googlesource.com/c/1357899Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/62c2383b006d..4bc9893eed87 Created with: gclient setdep -r src-internal@4bc9893eed87 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I03ea70135d7783831b51d552de1bea3b8c0dd422 Reviewed-on: https://chromium-review.googlesource.com/c/1357879Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/480454475db7..62c2383b006d Created with: gclient setdep -r src-internal@62c2383b006d The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: I9dac876007d538d04e65a967ef80e1093e5aabb2 Reviewed-on: https://chromium-review.googlesource.com/c/1357738Reviewed-by:
-
