- 26 Mar, 2018 24 commits
-
-
Ben Wells authored
This reverts commit d03adf5a. Reason for revert: This has caused some tests to fail flakily and reflect a crash that could happen in the wild. See http://crbug.com/825448 Original change's description: > RDH: Ensure there's at most one LoadInfoList in flight. > > ResourceDispatcherHost pushes pending load state of all frames to the UI > thread once every 250 milliseconds when there's a pending load. This > happens even when the UI thread is blocked. Apparently it's causing an > OOM when the UI thread is blocked. Whatever is blocking the UI thread > is another issue entirely, but we shouldn't use unbounded memory in the > browser process. This CL prevents load state updates from being sent > until the previous set was ACKed by the UI thread. > > Bug: 824869 > TBR: jam@chromium.org > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo > Change-Id: I3b68522c5281d477d3a621ac02e5df1f75153d99 > Reviewed-on: https://chromium-review.googlesource.com/978383 > Commit-Queue: Matt Menke <mmenke@chromium.org> > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > Reviewed-by: Charlie Harrison <csharrison@chromium.org> > Cr-Commit-Position: refs/heads/master@{#545616} TBR=jam@chromium.org,mmenke@chromium.org,csharrison@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 824869 Change-Id: I350dd7b357c32ffc7fb85a2417afaf779552ff77 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo Reviewed-on: https://chromium-review.googlesource.com/979674Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Ben Wells <benwells@chromium.org> Cr-Commit-Position: refs/heads/master@{#545741}
-
Joel Hockey authored
Added ClickBreadcrumbs user action for click in breadcrumb. Fixed handling of MockFileSystem root to always include trailing slash. The root dir is referenced in the breadcrumb and causes errors in tests with inconsistency of trailing slash. Bug: 824607 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I5ff72f4d2542c25f87fd495bdb088d0d3315424f Reviewed-on: https://chromium-review.googlesource.com/977381 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Sasha Morrissey <sashab@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Naoki Fukino <fukino@chromium.org> Cr-Commit-Position: refs/heads/master@{#545740}
-
Dominic Battre authored
The test fails flakily on Linux, Windows and ChromeOS. See bug for details. TBR=foolip@chromium.org, dmazzoni@chromium.org Bug: 825735 Change-Id: I5953f23c9c87e7b4ab2b0a6b9fd9d604a1bf27c3 Reviewed-on: https://chromium-review.googlesource.com/979799Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#545739}
-
Tetsui Ohkubo authored
When notification inline settings is opened from the top right gear icon using by keyboard, it crashed as animation requires the event to be LocatedEvent but it's not. TEST=manual BUG=823646 Change-Id: Ia683de86e042f010ac4bb0ee645fff170547b9fa Reviewed-on: https://chromium-review.googlesource.com/974922 Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Cr-Commit-Position: refs/heads/master@{#545738}
-
Blake O'Hare authored
Was trying to fix something in this code for an unrelated bug and came across a few things that could be improved: * There were too many stateful booleans making the code unnecessarily complex. * The type of event that initialized the drag should be in the DragDescriptor, because it describes the drag and also has the same life cycle. * Flatten complicated if statements into chains of if/else's that only use simple conditions. * Use a switch statement for the event type. Change-Id: I74712df2502960c6a98be0a705a5ced94a61ec75 Reviewed-on: https://chromium-review.googlesource.com/979378Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: Blake O'Hare <blakeo@chromium.org> Cr-Commit-Position: refs/heads/master@{#545737}
-
Joel Hockey authored
Fix MockFileSystem to delete entries rather than nulling them. As null, the key is still iterable which causes errors. Make root path consistent to always have trailing slash which matches prod behaviour. Set default size/date metadata for MockDirectoryEntry. Put all test helper methods in 'test' namespace. Replace waitUntil with repeatUntil/pending from integration_tests/test_util.js which provides better error reporting. Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Ie648388a7d6fe6c79951d5b4330234c378ffe2ee Reviewed-on: https://chromium-review.googlesource.com/965722 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Naoki Fukino <fukino@chromium.org> Cr-Commit-Position: refs/heads/master@{#545736}
-
Yoshifumi Inoue authored
This patch introduces tests for hanling of "inline-block" and "float" of |NGInlineNode::CollectInlines()| to avoid regression for improving code health. This patch is a preparation the patch[1]. [1] http://crrev.com/c/737981 Simplify word granularity handling Bug: 778507 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ifead65d6df83a19dbe2b82b509ef39427b56962c Reviewed-on: https://chromium-review.googlesource.com/979751 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#545735}
-
Dominic Battre authored
See bug for details. TBR=hubbe@chromium.org,dalecurtis@chromium.org notry=true Bug: 754986 Change-Id: I33b05a30137c2c793d1704242dbb28d15c5aefe3 Reviewed-on: https://chromium-review.googlesource.com/979800Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#545734}
-
Yue Li authored
Bug: 824566 Test: Manual Change-Id: I58609375c31f9fc86e16ef2e214747ced8f24218 Reviewed-on: https://chromium-review.googlesource.com/974572 Commit-Queue: Yue Li <updowndota@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#545733}
-
Luciano Pacheco authored
Accessibility fix for "Open With" dialog that wasn't being read by Chromevox. Change DefaultTaskDialog to set tabindex=-1 for dialog items, so they can be navigated via JS focus() method, but not via TAB key. Change cr.ui.List to issue an focus to the item when navigated via keyboard arrow up/down. Dialog items already have the correct text to be read, see bug for screenshot. Bug: 435010 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I2abc1d2d3d6cb6e78a373ccc51c79e34a0b756bd Reviewed-on: https://chromium-review.googlesource.com/968004Reviewed-by:
Naoki Fukino <fukino@chromium.org> Reviewed-by:
Sasha Morrissey <sashab@chromium.org> Commit-Queue: Luciano Pacheco (SYD) <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#545732}
-
Chandan Padhi authored
This CL is a follow-up on https://crrev.com/c/956383. Bug: 817769 Change-Id: I83a87fc0ee5889e9efa2c6e7a86ae8f2c6c70b90 Reviewed-on: https://chromium-review.googlesource.com/978225Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Chandan Padhi <c.padhi@samsung.com> Cr-Commit-Position: refs/heads/master@{#545731}
-
Dominic Battre authored
The media/color-profile-video-seek-filter.html fails flakily on Win7. See bug for details. notry=true TBR=chcunningham@chromium.org Bug: 825733 Change-Id: I42edc7907e4de80e2201689796de4ff5d10ff487 Reviewed-on: https://chromium-review.googlesource.com/979795Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#545730}
-
Darren Shen authored
When converting CSSCustomPropertyDeclaration to CSSUnparsedValues, we used to assume that CSSCustomPropertyDeclaration will always have a CSSVariableData, but it turns out that css-wide keywords are stored as a CSSValueID instead of a CSSVariableData. This patch handles css-wide keywords on CSSUnparsedValues correctly. We added a unit test and not a WPT since this is likely a blink-only implementation detail. Bug: 824740 Change-Id: Iefbdca4abc736562b81f5c6a3f0332975b842961 Reviewed-on: https://chromium-review.googlesource.com/977141 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#545729}
-
Adam Rice authored
Previously network::WebSocket objects were stored as raw pointers in a set and deleted manually. Use a set<unique_ptr<WebSocket>, UniquePtrComparator> instead, making ownership explicit and reducing the risk of leaking. Change-Id: I0337551d8fd073341241723538cf9864eb206c87 Reviewed-on: https://chromium-review.googlesource.com/978282Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#545728}
-
Darren Shen authored
TBR=dmazzoni@chromium.org Bug: 825429 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I677963581b6594c014f05a717330f4b5f827a372 Reviewed-on: https://chromium-review.googlesource.com/979745 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545727}
-
Giovanni Ortuño Urquidi authored
Bug: 788251 Change-Id: I328cb3c1c812fab565eafc4009e0210653e236c7 Reviewed-on: https://chromium-review.googlesource.com/958768Reviewed-by:
Trent Apted <tapted@chromium.org> Reviewed-by:
Matt Giuca <mgiuca@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#545726}
-
Matt Falkenhagen authored
This reverts commit d260e9cf. Reason for revert: In Windows Canary versions since 67.0.3377.0, where this commit landed, IO thread hang reports have spiked dramatically. It is now the #1 browser crash report on Windows Canary at 33% of reports. I'm speculatively reverting this to see if the crash rate heals. Original change's description: > Refactor BrowserThreadImpl, BrowserProcessSubThread, and BrowserMainLoop > > This brings back the invariant that BrowserThread::IO isn't available > before BrowserMainLoop::CreateThreads(). This was broken to fix issue > 729596 to bring up the thread earlier for ServiceManager but it is > important that code that posts to BrowserThread::IO statically have an > happens-after relationship to BrowserMainLoop::CreateThreads(). Exposing > it statically earlier put that invariant at risk. > > Thankfully fixing issue 815225 resulted in finally reaching the long > sought goal of only having BrowserThread::UI/IO. Now that the IO thread > is also kicked off before it's named statically, BrowserThreadImpl no > longer needs to be a base::Thread, hence this refactoring. > > Before this CL: > * BrowserThreadImpl was a base::Thread > (could be a fake thread if SetMessageLoop was used) > * BrowserProcessSubThread was a BrowserThreadImpl > (performed a bit more initialization) > * BrowserProcessSubThread was only used in production (in > BrowserMainLoop) > * BrowserThreadImpl was used for fake threads (BrowserMainLoop for > BrowserThread::UI) and for testing (TestBrowserThread(Impl)). > * BrowserThreadImpl overrode Init/Run/CleanUp() from base::Thread to > perform some sanity checks as well as drive IOThread's Delegate (ref. > BrowserThread::SetIOThreadDelegate()) > * BrowserProcessSubThread re-overrode Init/Run/CleanUp() to perform > per-thread //content initialization (tests missed out on that per > TestBrowserThread bypassing BrowserProcessSubThread by directly > subclassing BrowserThreadImpl). > > With this CL: > * BrowserThreadImpl is merely a scoped object that binds a provided > SingleThreadTaskRunner to a BrowserThread::ID. > * BrowserProcessSubThread is a base::Thread and performs all of the > initialization and cleanup specific to //content (this means it now > also manages BrowserThread::SetIOThreadDelegate()) > * BrowserProcessSubThread can be brought up early before being bound to > a BrowserThread::ID (BrowserMainLoop handles that through > BrowserProcessSubThread ::RegisterAsBrowserThread()) > > Unfortunate exceptions required for this CL: > * IOThread::Init() (invoked through BrowserThreadDelegate) perfoms > blocking operations this was previously performed before installed > the ThreadRestrictions on BrowserThread::IO. But now that //content > is initialized after bringing up the thread, a > base::ScopedAllowBlocking is required in scope of IOThread::Init(). > * TestBrowserThread previously bypassing BrowserProcessSubThread by > directly subclassing BrowserThreadImpl meant it wasn't subject to > ThreadRestrictions (unfortunate becomes it denies allowance > verification to product code running in unit tests). Adding it back > causes DCHECKs, as such > BrowserProcessSubThread::AllowBlockingForTesting was added to allow > this CL to pass CQ. > > Of note: > * BrowserProcessSubThread is still written as though it supports many > BrowserThread::IDs but in practice it's mostly always > BrowserThread::IO (except in ThreadWatcherTest I think). This change > was big enough that I didn't bother also breaking that > generalization. > * BrowserThreadImpl's constructor was made private to ensure only > BrowserProcessSubThread and a few select callers get to drive it (to > avoid previous missed initialization issues) > * Atomics to manage BrowserThread::SetIOThreadDelegate were removed. > Restriction was instead added that this only be called before > initialization and after shutdown (this was already the case). > > Follow-ups to this CL: > * //ios duplicates this logic and will need to undergo the same change > as a follow-up > * Fixing ios will allow removal of base::Thread::SetMessageLoop hack :) > * Removing BrowserThreadGlobals::lock_ to address crbug.com/821034 will > be much easier > * BrowserThread post APIs should DCHECK rather than no-op if using a > BrowserThread::ID before it's registered. > > Bug: 815225, 821034, 729596 > Change-Id: If1038f23079df72203b1e95c7d26647f8824a726 > Reviewed-on: https://chromium-review.googlesource.com/969104 > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > Commit-Queue: Gabriel Charette <gab@chromium.org> > Cr-Commit-Position: refs/heads/master@{#544440} TBR=gab@chromium.org,jam@chromium.org NOPRESUBMIT=true # Not skipping CQ checks because original CL landed > 1 day ago. # falken: Skipping presubmit to use deprecated ThreadResrictions::DisallowWaiting(). Bug: 815225, 821034, 729596 Change-Id: I2be97c5d8183497c005ab397c871f625b034d850 Reviewed-on: https://chromium-review.googlesource.com/979752 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#545725}
-
Khushal authored
Change a few DCHECKs to CHECKs to validate if some crashes are resulting from using unlocked images, or incorrectly unlocking them earlier. R=enne@chromium.org, ericrk@chromium.org Bug: 802976 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ibe0b9ef6ac52e6fafc9fd2670e20a9eefac17234 Reviewed-on: https://chromium-review.googlesource.com/979160 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#545724}
-
Chih-Yu Huang authored
Originally, the thread to update parameter "V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME" is different from QBUF the frame, so we cannot make sure the parameter is updated right before the key frame is QBUF. This CL queues the parameter |force_keyframe| with the frame, and update the parameter before QBUF the frame. BUG=b:74501913 TEST=pass GTS RtcVideoCodecTest#testRequestSyncFrameH264 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;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I1733f8ee474a0adeb8a31e6d196fdf27596a9f57 Reviewed-on: https://chromium-review.googlesource.com/958791 Commit-Queue: Chih-Yu Huang <akahuang@chromium.org> Reviewed-by:
Pawel Osciak <posciak@chromium.org> Cr-Commit-Position: refs/heads/master@{#545723}
-
Eugene But authored
This is an existing histogram logged for the Old Download Manager. The histogram is already a part of histograms.xml file. Bug: 791806 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I720221f6a5b395d947a96a99ce7e4d6fe7bee09e Reviewed-on: https://chromium-review.googlesource.com/979267Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#545722}
-
Darren Shen authored
We try to support as many font properties as possible. However, several font properties have not been implemented in Blink yet. Also, the computed value for font-stretch is wrong (it should be as specified, and no rounding should occur). Spec: https://drafts.css-houdini.org/css-typed-om-1/#reify-stylevalue Bug: 820299 Change-Id: I744d03a08856bd6d0df6bd07230ec80138e6e3b7 Reviewed-on: https://chromium-review.googlesource.com/977247Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545721}
-
Daniel Bratell authored
In some (extreme) jumbo configurations on Mac two kBufferSize constants ended up in the same translation unit and caused a compilation error. This patch gives them unique names to not cause any future problems. Change-Id: I96d5e51024ff99fcb838346726aa1635127841eb Reviewed-on: https://chromium-review.googlesource.com/978209 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545720}
-
Kent Tamura authored
Remove DeprecatedDataLogF() usage from platform/heap/. Bug: 720442 Change-Id: Iac1a3ca91c932001ecb7f0e6beee3842108668c1 Reviewed-on: https://chromium-review.googlesource.com/977843Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545719}
-
Daniel Bratell authored
There is a kLeftToRight in OSX's SDK and in WTF::Unicode. If WTF::Unicode is imported into global scope those might clash and this happens in some non-standard (extreme) jumbo configurations. Since "using namespace" isn't allowed per the coding standard, this just adds the WTF::Unicode namespace to those symbols that need it. Change-Id: I97c59e5ffed7d2bd0f8340f5d14b69dc532175d6 Reviewed-on: https://chromium-review.googlesource.com/978205 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545718}
-
- 25 Mar, 2018 15 commits
-
-
Daniel Bratell authored
There is both a ::testing namespace and a blink::testing namespace and if you inside namespace blink says "testing", which one you get depends on what the compiler knows. In jumbo builds compilers often know about both namespaces and will assume you mean ::blink::testing. To be sure to get ::testing, you need to prefix it with ::. In the long run ::blink::testing should probably be renamed. Its name violates the rule that no sub namespace should have the same name as a common top level namespace. Change-Id: I60857ebd08d4b35ce56212d03b4ed63045803402 Reviewed-on: https://chromium-review.googlesource.com/978004 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545717}
-
Kent Tamura authored
crrev.com/545269 added AdTracker to CoreProbes.json5, in which we don't support snake_case source files yet. Bug: 578345 Change-Id: I92e59040a7c413e56459b3c9f4faa02505d4738d Reviewed-on: https://chromium-review.googlesource.com/977204Reviewed-by:
Quinten Yearsley <qyearsley@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545716}
-
Kent Tamura authored
We know these CLs won't pass presubmit checks. We're going to land these CLs while the tree is closed. Bug: 578345 Change-Id: I75549f683f61a1cd6cf8d5711c106bd49b32e8f7 Reviewed-on: https://chromium-review.googlesource.com/974670Reviewed-by:
Quinten Yearsley <qyearsley@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545715}
-
https://skia.googlesource.com/skia.git/+log/33477889c58b..9b67c565cc7b $ git log 33477889c..9b67c565c --date=short --no-merges --format='%ad %ae %s' 2018-03-25 update-skps Update SKP version Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=mtklein@chromium.org Change-Id: Ic12d58021e8c83d45abce9bdc5cc184ccf49e023 Reviewed-on: https://chromium-review.googlesource.com/979600Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#545714}
-
Kurt Horimoto authored
The behavior of TapWebViewElementWithId() for links that close a WebState is flaky on both simulator and device, regardless of whether the Phase 1 UI Reboot flag is enabled. This CL updates FullscreenTestCase.testShowHeaderWhenChildTabCloses to check for the error code only if the link tap is unsuccessful. Note that the closure of the Tab and the visibility of the toolbar is still verified after this occurs, so the test will still catch fullscreen regressions after this change. Bug: 812664 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ia56293763e185eeb615a5f734aa9a3a473f0b424 Reviewed-on: https://chromium-review.googlesource.com/974791 Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#545713}
-
https://webrtc.googlesource.com/src.git/+log/0bf0c3d7aa27..b0ba558c966c $ git log 0bf0c3d7a..b0ba558c9 --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org 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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I7b89bc4df42e0fe50ad39973b7f0c2ae30789757 Reviewed-on: https://chromium-review.googlesource.com/979608Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#545712}
-
Zhenyao Mo authored
This is because the actual glDeleteBuffers() might be delayed. BUG=822976 TEST=gpu_unittests R=kbr@chromium.org,piman@chromium.org 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;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Idc0504817e8d6d776cf6464a1acda3b0836b9a55 Reviewed-on: https://chromium-review.googlesource.com/978473Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#545711}
-
Quinten Yearsley authored
I believe this might be dead code; I'm not sure if the layout test runner is used to run any Blink performance tests. The last related change was last year: https://codereview.chromium.org/2734823006 Before that, all changes seem to be from about 5 years ago. Change-Id: Ib1a23055391112c83b97e000707f0b2f333040e5 Reviewed-on: https://chromium-review.googlesource.com/966484 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#545710}
-
Chris Kuiper authored
This sets a proper default ducking multiplier used in Chromium's MediaSession (see Chromium change 942055 for reference). Two cases: 1) On AThings speakers running CMA backend, which does its own ducking, disable ducking in the Chromium MediaSession by setting its ducking multiplier to 1.0. 2) For speakers not running CMA backend and relying on the Chromium MediaSession to duck, set an appropriate ducking multiplier (-30dB) that is inline with Cast's ducking levels [-35..-20]dB. Note that this is a simplification of Cast's ducking logic and more fine-tuning of this is desirable. Bug: internal b/69630398, internal b/73907369 Test: Ran on Android Things speakers w/ and w/o CMA backend, observed proper ducking. Change-Id: I5fe5a7e46750b88a7d44af1b38ec3f094a7c387d Reviewed-on: https://chromium-review.googlesource.com/979261 Commit-Queue: Chris Kuiper <ckuiper@chromium.org> Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#545709}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/191c7ea0..0351f2cb Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I6d77f729d2c1decc55eaf28eb10d6424f1ffa28e Reviewed-on: https://chromium-review.googlesource.com/979202Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#545708}
-
https://chromium.googlesource.com/chromiumos/chromite.git/+log/e6139afa10f8..44123785ca9a $ git log e6139afa1..44123785c --date=short --no-merges --format='%ad %ae %s' 2018-03-24 ihf chromeos-config: mark eve-arcnext-chrome-pfq important. 2018-03-23 achuith cros_vm: Determine SDK version outside SDK shell. Created with: roll-dep src/third_party/chromite BUG=chromium:825539,chromium:823996 The AutoRoll server is located here: https://chromite-chromium-roll.skia.org 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: Icb8dcad2d3ee70b331e2446f9f873e2c21c385d8 Reviewed-on: https://chromium-review.googlesource.com/979598Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#545707}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/9ae313c8..191c7ea0 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I324e0c21be55a90414e0ee80e4e15444b25b895e Reviewed-on: https://chromium-review.googlesource.com/979200Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#545706}
-
Andrew Grieve authored
Change-Id: Ie1112d1c1c657a55b5fee9b2732528c49f2f1b26 Reviewed-on: https://chromium-review.googlesource.com/978449Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#545705}
-
Christopher Grant authored
I used a grep/awk/wc command to find constants that existed in only a single spot. BUG= R=vollick 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;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I79b277dd15a5442cf6a72fc6bc32bed04a282ded Reviewed-on: https://chromium-review.googlesource.com/977953 Commit-Queue: Christopher Grant <cjgrant@chromium.org> Reviewed-by:
Ian Vollick <vollick@chromium.org> Cr-Commit-Position: refs/heads/master@{#545704}
-
https://webrtc.googlesource.com/src.git/+log/883f470d605d..0bf0c3d7aa27 $ git log 883f470d6..0bf0c3d7a --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org 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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I6ebeae9524531ff6960ebc37bef746c7f469a830 Reviewed-on: https://chromium-review.googlesource.com/979404Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#545703}
-
- 24 Mar, 2018 1 commit
-
-
Ian Vollick authored
This CL changes constants and strings to match the spec. Bug: None 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;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I2d94a15c72e247cfc047fc54e9c7cdeda3b4a4f6 Reviewed-on: https://chromium-review.googlesource.com/979411Reviewed-by:
Yash Malik <ymalik@chromium.org> Commit-Queue: Ian Vollick <vollick@chromium.org> Cr-Commit-Position: refs/heads/master@{#545702}
-