- 19 Aug, 2019 40 commits
-
-
Willie Koomson authored
Deprecates use of memory_instrumentation.mojom.GlobalMemoryDump struct in process.mojom and ArcProcessService. Uses new struct ArcMemoryDump instead. manager for Android memory footprint Bug: b:139190852 Test: Build cheet_x86 and flash betty-arcnext, check Chrome OS task Change-Id: Ib21dfcf8ab7c23dfd60573341dfdddbcb744f166 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749456 Commit-Queue: Willie Koomson <wvk@google.com> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#688212}
-
Sven Zheng authored
With this change, all DialogBrowserTest should be abled to verify pixel correctness. To use them as pixel test, add flag --browser-ui-tests-verify-pixels. TEST: browser_tests.exe --gtest_filter=PermissionDialogTest.* --browser-ui-tests-verify-pixels --enable-pixel-output-in-tests --build-revision=b6aaf42b --no-luci-auth I've approved the following images so these tests can pass now. https://chrome-gpu-gold.skia.org/detail?test=BrowserUiDialog_PermissionDialogTest_InvokeUi_protocol_handlers&digest=877f6df6101e926f24c5b9bc3cf111b3 https://chrome-gpu-gold.skia.org/detail?test=BrowserUiDialog_PermissionDialogTest_InvokeUi_camera&digest=cf09792802b243e0a33bf4d45e2e8047 I didn't start with test_browser_ui because most of the tests are inherited from test_browser_dialog. Next step: 1 Add some tests to fyi bots to monitor the stability. 2 Fix some tests that don't have stable UI. Eg disable animation for https://chrome-gpu-gold.skia.org/detail?test=BrowserUiDialog_AuthenticatorDialogViewTest_InvokeUi_default&digest=2442c011949e9f98f4442f066bb90e55 Bug: 958242 Change-Id: I7bc048b792a5e303e8ee948fda228fa664395ca1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756604 Commit-Queue: Sven Zheng <svenzheng@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#688211}
-
Adrienne Walker authored
Layers start at the origin and not in negative space and we should never need these values. This prevents rtree complexity and bounds overflow. Bug: 988590 Change-Id: I4fa77c11fc5f0411997e2697291b9e554958c9f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749703Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#688210}
-
Scott Violet authored
Adds logic to switch between LayoutFlexibleBox and LayoutDeprecatedFlexibleBox when clamping changes. This is necessary as LayoutDeprecatedFlexibleBox is the only place that currently provides support for clamping. BUG=993813 TEST=none Change-Id: I88dc4ce0195faf08870afeb9e8e5fce338a29476 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754922 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#688209}
-
Manu Cornet authored
This is not expected to result in any user-visible changes. Bug: 973482, 973446 Change-Id: I8cddfbaaff421db8e8824dcf25ee817b3f7ee894 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730960 Commit-Queue: Manu Cornet <manucornet@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#688208}
-
Gabriel Charette authored
Presubmit warnings found as part of touching many files in https://chromium-review.googlesource.com/c/chromium/src/+/1756247 R=hansberry@chromium.org, msw@chromium.org Bug: 992483 Change-Id: I76ceb6ded41b61a27ea0fd0b0cd7d7ee7d66596f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757507 Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#688207}
-
Michael Thiessen authored
No functionality changes intended, this is simply cleanup. getModelAt was only exposed for testing, and the API contract was confusing (SingleTabModelSelector always just returned the index 0 model). Change-Id: I7f18ad407e14540de180c7f5b8d624e3148266af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749845Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#688206}
-
Garrett Beaty authored
named-cache-clobber.py can be used to clobber any named cache on machines in any pool. The existing clobber.py was replaced with builder-cache-clobber.py, which renames the pool flag to bucket to more accurately indicate the expected value and removes the restriction on project. Change-Id: I7614330213c8e20a0c0e9ee4bb0498d3b2fbbb38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757888 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#688205}
-
Natalie Chouinard authored
In the Support Library Preference's onBindViewHolder, visibility toggling is handled for both title and summary empty TextViews, so removing some now redundant logic. There are no TextMessagePreferences which contain links in the title, and the LinkMovementMethod was breaking DPad navigation on screens where it was set, so removing that as well. See https://crbug.com/993368. Bug: 993368 Change-Id: I702fc08e563e544e9ad774c2b05dcdd070a74678 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757390Reviewed-by:
-
Xiaocheng Hu authored
Bug: 978682 Change-Id: I65c38a7b5978034c4c477e68d29edaa2852d09af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758299Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#688203}
-
Tibor Goldschwendt authored
Change-Id: I5de49029ca6904d034ecfaa01d780351f5ce22ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761189 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Eric Stevenson <estevenson@chromium.org> Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Eric Stevenson <estevenson@chromium.org> Cr-Commit-Position: refs/heads/master@{#688202}
-
Francois Doray authored
The original CL https://chromium-review.googlesource.com/c/chromium/src/+/1679434 was reverted because of failures on test end on Mac OS 10.11. This CL simply disables that check on Mac, so we can benefit from process priority check on other platforms ASAP. See diff: https://chromium-review.googlesource.com/c/chromium/src/+/1760873/2..3/base/test/test_suite.cc This CL verifies that a test process is not backgrounded when it is launched and before/after each test. The goal is to avoid having tests that assume they run at normal priority be disabled because of other misbehaving tests (e.g. https://crbug.com/931721). Bug: 931721 Change-Id: Ib60d728c960f84026c84f24395d38847c1941573 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760873Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#688201}
-
Yaron Friedman authored
Bo knows this code and the only client is content/renderer/input. Input folks ought to be better reviewers Change-Id: Ie5b0042378eb38cb08e7f29a6ec4c20f2f4cc3b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758657 Commit-Queue: Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#688200}
-
Anna Malova authored
Bug: 994758 Change-Id: Ic4d82f03ec8b0cb7cc19b4e5981f154d19c37334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758082Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Anna Malova <amalova@chromium.org> Cr-Commit-Position: refs/heads/master@{#688199}
-
Xi Han authored
This is a follow up CL for https://crrev.com/c/1758500. In this CL, caching the native flags is called when native is loaded in ServiceManager only mode, including: - ServiceManagerForDownload - ServiceManagerForBackgroundPrefetch Bug: 984559,995355 Change-Id: I51b00b3be048dc6ec377eeef0f81bbc0ce4e9023 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1759682 Commit-Queue: Xi Han <hanxi@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/8133374cb7fe..4935770daa8e git log 8133374cb7fe..4935770daa8e --date=short --no-merges --format='%ad %ae %s' 2019-08-19 tsepez@chromium.org Initialize widget handlers from topmost fpdfsdk. 2019-08-19 tsepez@chromium.org Avoid casting to CPDFXFA_Context just to get form type. Created with: gclient setdep -r src/third_party/pdfium@4935770daa8e The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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=pdfium-deps-rolls@chromium.org Bug: None Change-Id: I8bd5c37c009f066f76e1d50c714f56964372c6c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761000Reviewed-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@{#688197}
-
Ben Mason authored
This reverts commit 2b751bd7. Reason for revert: Crash on launch Original change's description: > JNI refactor: @NativeMethods conversion (//chrome/android/features). > > To create this change: > * cd chrome/android/features > * base/android/jni_generator/jni_refactorer.py -R --nonstatic > * base/android/jni_generator/jni_refactorer.py -R > * Change the native side of VrShellDelegateJni#recordVrStartAction > to not pass the Java object > > Bug: 929661 > Change-Id: I1d2c57e0f7a30a8b7e50e9e3ce905172cbb761cb > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749737 > Commit-Queue: Eric Stevenson <estevenson@chromium.org> > Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> > Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Auto-Submit: Eric Stevenson <estevenson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#687674} TBR=agrieve@chromium.org,estevenson@chromium.org,tiborg@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 929661 Change-Id: I60ffe465a69470b20d5785b291a13a0819bb2a08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1759892 Commit-Queue: Eric Stevenson <estevenson@chromium.org> Reviewed-by:
Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#688196}
-
Alex Keng authored
This CL enables <input type=radio/checkbox> to render high contrast colors when high contrast mode is enabled. A test is added in fast/forms/controls-new-ui-high-contrast. Note the test is verifying if we are correctly using system colors in high contrast mode and since we don't really change system setting for HC in webtests, the results colors are still black/grey/white (in higher contrast) instead of black/white/green. Bug: 994219 Change-Id: Ia798503ff040ce6b479a2845797118f7869c7ef3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756209 Commit-Queue: Alex Keng <shihken@microsoft.com> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#688195}
-
Eric Foo authored
This is CL is generated by a script. Data is pulled from review conducted in Q2 2019. See https://tinyurl.com/yxau5sc4 for context. Please review and LGTM before July 16th or the CL will be submitted as-is. TBR=dtrainor@chromium.org, jshin@chromium.org, pmonette@chromium.org NOTRY=true Bug: 977050 Change-Id: I1bf790cf0957c912382787dec1b100651ff6b0b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1699950Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Patrick Monette <pmonette@chromium.org> Reviewed-by:
Jungshik Shin <jshin@chromium.org> Commit-Queue: Eric Foo <efoo@chromium.org> Auto-Submit: Eric Foo <efoo@chromium.org> Cr-Commit-Position: refs/heads/master@{#688194}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/3f7932e73316..8566dda51b42 git log 3f7932e73316..8566dda51b42 --date=short --no-merges --format='%ad %ae %s' 2019-08-19 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-08-19 skia-autoroll@skia-public.iam.gserviceaccount.com Roll skia/third_party/skcms 958fec279ed5..d931999c3afd (1 commits) 2019-08-19 egdaniel@google.com Remove some unused GrPixelConfig functions. Created with: gclient setdep -r src/third_party/skia@8566dda51b42 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=egdaniel@google.com Bug: chromium:None Change-Id: I63baa0d8436797a464ad063b4d4288d01aaed70a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761001Reviewed-by:
-
Gabriel Charette authored
Per https://chromium-review.googlesource.com/c/chromium/src/+/1756247/2/chrome/browser/metrics/perf/heap_collector_unittest.cc#695 this is migrated on its own because of the non-trivial requirement to avoid formatting away intentional trailing whitespaces. Edit: Turns out trailing whitespace formatting was my editor's fault not git cl format. Simple one-line migration in latest patch set. R=gmx@chromium.org Bug: 992483 Change-Id: I8f6331ce2c187b41f1f541fbe03884a9138cfff1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1759145 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Gabriel Marin <gmx@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#688192}
-
Fred Mello authored
Implemented Strategy Pattern so that the class can be tested more easily. Moved all external dependencies into an injectable class (SplitCompatStrategy). Removed "spying" from unit tests. Bug: 949729 Change-Id: If35af947f207a429e1d9badeb5b1b1fdb978e5ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752504Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Peter Wen <wnwen@chromium.org> Commit-Queue: Fred Mello <fredmello@chromium.org> Cr-Commit-Position: refs/heads/master@{#688191}
-
Dirk Pranke authored
run_web_tests supported the --gtest_repeat, --gtest_also_run_disabled_tests, and --gtest_filter flags for compatibility with FindIt; however FindIt eventually moved to using the --isolated-script-test flags instead, and these flags should no longer be used or needed, so this CL removes them. This is a prelude to cleaning up and implementing proper support for multiple --isolated-script-test-filter args. Bug: 893235, 994943 Change-Id: Id7a8ef5f43855b54eeb76193ceca45310b426890 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1759138Reviewed-by:
Chan Li <chanli@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Reviewed-by:
Rakib Hasan <rmhasan@google.com> Commit-Queue: Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#688190}
-
Tibor Goldschwendt authored
Change-Id: If4da40d267aeb4a4ee8d099a95d502952abf6dc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761005 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Yaron Friedman <yfriedman@chromium.org> Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
-
Ian Kilpatrick authored
This also removes LayoutBox from the code, instead preferring NGLayoutInputNode. There should be no behaviour change. Bug: 726125 Change-Id: I532c5078806151f6336523f742bf62e76a374bcd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761067Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#688188}
-
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: I963720b3c1e18eee0dfe29e3ff856e4dc1a906ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760998Reviewed-by:
-
Krishna Govind authored
This reverts commit 8fb37f86. Reason for revert: Browser crash, bug 995264 Original change's description: > [BackgroundTaskScheduler] TaskInfo refactoring > > The BackgroundTaskScheduler does not offer at the moment the possibility of scheduling a task at an exact moment. In preparation for this feature, the existing code is going to be updated first. > > This CL refactors the way in which specific task information is kept. A more object-oriented approach is implemented, based on the discussion in this Design doc: https://docs.google.com/document/d/1o9BS5qwv10QVN3Df6W2m4QKjSo1DXdGIgLf8p2l0PYc/edit?usp=sharing. Changes have been made only in the way timing info for a task is kept and not in the way pre-requisites information is kept. Updates have also been added to the test files. > > This change does not affect the interface exposed by the TaskInfo class. > > TBR=rouslan@chromium.org > > Bug: 970160 > Change-Id: I2985ca68da4e6db18f47e0fd1769db3138850cb0 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1707365 > Commit-Queue: Richard Knoll <knollr@chromium.org> > Reviewed-by: Tommy Nyquist <nyquist@chromium.org> > Reviewed-by: Mugdha Lakhani <nator@chromium.org> > Reviewed-by: Richard Knoll <knollr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#687603} TBR=nyquist@chromium.org,nator@chromium.org,knollr@chromium.org,ioanastefan@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 970160 Change-Id: I199f9c5245ac659c733599cec3558d780f21be19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761050Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#688186}
-
Victor Fei authored
This is a reland of 0297659d The change was reverted because newly added unittest AutofillPopupControllerA11yUnitTest::FireControlsChanged fails on linux with Control Flow Integrity (CFI) turned on. The reason it fails CFI is because on tear down of the test, AutofillPopupControllerImpl::Hide() performs a static cast of AutofillDriver to ContentAutofillDriver. Since the MockAutofillDriver used in the a11y unittests does not derive from ContentAutofillDriver, with CFI turned on, an exception is caused at this cast. The fix for this is for MockAutofillDriver in AutofillPopupControllerUnitTest to be derived from ContentAutofillDriver. Original change's description: > Stablizing Mac autofill accessibility when popup show/hides > > This is a follow up change of CL:1667787, which introduced > AutofillPopupControllerImpl::FireControlsChangedEvent for autofill > popup accessibility. > > On Mac and potentially other platforms, when accessibility is > enabled, upon invoking autofill popup and FireControlsChangedEvent > we end up dereferencing a nullptr of AxPlatformNode due to > Mac does not have a complete implementation of AxPlatformNode yet. > > This CL fixes the above by adding a check for AxPlatformNode in > FireControlsChangedEvent. > > Changes: > 1. Introduced a check for invalid AxPlatformNode in > AutofillPopupControllerImpl::FireControlsChangedEvent to return > early from firing event. > 2. Added associated unit tests for FireControlsChangedEvent. > 3. Exposed GetWebContentsPopupControllerAxId virtual to > AutofillPopupDelegate.. > > Bug: 986587 > Change-Id: I9a6ed49330a9ea9d7d4e5483c3ee06d5675919ee > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1714297 > Commit-Queue: Victor Fei <vicfei@microsoft.com> > Reviewed-by: Evan Stade <estade@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Ian Prest <iapres@microsoft.com> > Reviewed-by: Nektarios Paisios <nektar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#686461} Bug: 986587 Change-Id: I8e7772743d713329e871f8e130010cd7af321463 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752687Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
Ian Prest <iapres@microsoft.com> Commit-Queue: Ian Prest <iapres@microsoft.com> Cr-Commit-Position: refs/heads/master@{#688185}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a65b81326a8a..4dfd57b8be2c Created with: gclient setdep -r src-internal@4dfd57b8be2c The AutoRoll server is located here: https://skia-autoroll.corp.goog/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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:b/139144240,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:994067,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:None,chromium:b/139144240 Change-Id: I135646b29268c34858fee42bbf14d6754dff485c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761009Reviewed-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@{#688184}
-
Xida Chen authored
This CL moves filter-interpolation-*.html from animations/interpolation to external/wpt/css/filter-effects/animation. Some of the test cases in animations/interpolation/ already exist in css/filter-effects/animation/, and hence they are not added again. We only add the ones that aren't there yet. Bug: 900581 Change-Id: I34b93a035885c9de12b86c22e508039bd47d0d30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760726Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#688183}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/185243b33522..fdf38802a684 git log 185243b33522..fdf38802a684 --date=short --no-merges --format='%ad %ae %s' 2019-08-19 hofbauer@webrtc.org Make "WebRTC-BweAllocProbingOnlyInAlr/Enabled/" default and remove key. 2019-08-19 sprang@webrtc.org Remove usage of RtpRtcp::SetSSRC() in video/ Created with: gclient setdep -r src/third_party/webrtc@fdf38802a684 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. TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:951299 Change-Id: I801ec8af37871c36038cb685ebd8794d31a4dc63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760895Reviewed-by:
-
Anna Malova authored
Bug: 994321 Change-Id: I8d8e40772563e12d986d28b107841e6933c33c7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760924Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Anna Malova <amalova@chromium.org> Cr-Commit-Position: refs/heads/master@{#688181}
-
Michael Thiessen authored
Bug: 993149 Change-Id: I0d2cb6238d3adf421f074c74124191898f901af7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758923 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#688180}
-
Sophie Chang authored
Bug: 969558 Change-Id: I8755c18f37b936663ad3a6df6fb5122397bf1337 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756713 Commit-Queue: Sophie Chang <sophiechang@chromium.org> Reviewed-by:
Joshua Bell <jsbell@chromium.org> Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Cr-Commit-Position: refs/heads/master@{#688179}
-
Sahel Sharify authored
The test was disabled on chromeOS, this cl disables the test on other platforms as well. flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=interactive_ui_tests%20(with%20patch)&tests=SitePerProcessTextInputManagerTest.TrackStateWhenSwitchingFocusedFrames TBR=wjmaclean@chromium.org NOTRY=TRUE Bug: 704994 Change-Id: If7b9f6662d7b35fcfc0b9cacec2d215baccfb928 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1759686Reviewed-by:
Sahel Sharify <sahel@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#688178}
-
Caleb Raitto authored
- Clarify why the read of runnable.mExecutedInline is safe. - Fix bad wrapping in an existing comment. - Clarify why writing "runnable.mCallingThread = null;" is safe. Change-Id: Iefb87004f106e400dfa02a61fa1d6f1120d2fbe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743278Reviewed-by:
Paul Jensen <pauljensen@chromium.org> Commit-Queue: Caleb Raitto <caraitto@chromium.org> Cr-Commit-Position: refs/heads/master@{#688177}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/303ddb5c8807..aad8cfca57fd git log 303ddb5c8807..aad8cfca57fd --date=short --no-merges --format='%ad %ae %s' 2019-08-19 chrisforbes@google.com Add feature support check for VkPhysicalDeviceMultiviewFeatures Created with: gclient setdep -r src/third_party/swiftshader@aad8cfca57fd The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=swiftshader-team+autoroll@google.com Bug: chromium:b/139528538 Change-Id: I6e323cb5048ff01f906ef0307a838487dfb49ad6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761008Reviewed-by:
-
Juan Antonio Navarro Perez authored
Script no longer works as it dependes on the no longer existing WPR implementation in python. Bug: 921000 Change-Id: I160937cfe3734ee950ba95ece2831793c2429ade Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760216 Auto-Submit: Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Reviewed-by:
-
Tom McKee authored
The PageLoad.PaintTiming.ParseStartToFirstContentfulPaint histogram was marked as a 'heartbeat' metric in histograms.xml but is not considered a heartbeat metric anymore. This change removes the stale 'heartbeat' designation and also sets an expiry date of about one year. This way, stale histograms get taken out of circulation eventually but not before owners have a chance to review. Bug: 991343 Change-Id: Iaf9b80f834230df7d4a09936150ab487d14bf1db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756394Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#688174}
-
A Olsen authored
Only slightly improves success detection at this stage, by adding Azure support - Ping and Okta are still pretty lacking - but makes room in the code for better success detection, and adds a unit test. Bug: 930109 Change-Id: I59a173095301f7c641031f79cb3a6c946c5efc09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754013Reviewed-by:
Lutz Justen <ljusten@chromium.org> Commit-Queue: A Olsen <olsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#688173}
-
