- 07 Nov, 2018 40 commits
-
-
Marc Treib authored
instead of defining a custom MockSyncService that isn't used as a mock. Bug: 859874 Change-Id: If1458426ff77a666a2be0dc08513a87b26ad76b0 Reviewed-on: https://chromium-review.googlesource.com/c/1322710Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#606063}
-
Aaron Krajeski authored
This prevents us from recording canvas size multiple times for the same canvas. Also confirmed that we are recording the correct numbers and move `isOffscreen` to an enum. Bug: 902000 Change-Id: Ic6e66ec960ae0166699280303a61b574c9320294 Reviewed-on: https://chromium-review.googlesource.com/c/1319180 Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Cr-Commit-Position: refs/heads/master@{#606062}
-
Sebastien Marchand authored
There's several singletons / global instances in c/b/rc that are leaked at shutdown, this is causing some issues in runs of unit_tests because we end up re-using them between different test runs that should be independent. This is currently preventing some feature to be enabled. This CL add a new ResourceCoordinatorParts class that encapsulate all these objects that should be created only once, an instance of this class is owned by the browser process. Change-Id: Ia64618b6f47052815d861ff6820d994f8a65cc64 Reviewed-on: https://chromium-review.googlesource.com/c/1290775Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Cr-Commit-Position: refs/heads/master@{#606061}
-
Christopher Grant authored
Previously, Monochrome used its own set of GN targets to package resources, analogous to the ones used for Chrome (some of which are the same used for non-Android platforms). This change moves both variants to use matching sets of template-generated targets. Later, when bundle-specific native libraries are added, this common template can be reused again. BUG=874584 Change-Id: Ia9c34cb0dfa8754207bdee146dbde47f9aca78d3 Reviewed-on: https://chromium-review.googlesource.com/c/1318418 Commit-Queue: Christopher Grant <cjgrant@chromium.org> Reviewed-by:
agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#606060}
-
Patricia Hongo authored
The existing sign out pref is written just once, which makes sense for Android EDU devices, but not for child accounts. These accounts may become unsupervised, in which case they should be able to sign out. Test: verified that the "Sign out of Chrome" button is hidden while an existing consumer account is supervised, and enabled after the account chooses to leave supervision. Didn't test on an Android EDU device yet. Bug: 894618 Change-Id: I81e4f75857bf7f8346ef4a48caa3e32edae95848 Reviewed-on: https://chromium-review.googlesource.com/c/1306654Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Commit-Queue: P H <phongo@chromium.org> Cr-Commit-Position: refs/heads/master@{#606059}
-
Camille Lamy authored
This CL adds a temporary check in that we have a valid FrameNavigationEntry. NavigationControllerImpl: :CreateNavigationRequestFromLoadParams to check Bug: 896028, 877654 Change-Id: Iaaf20e3eeb98e4ce284fa6a18a9a75d7d8016c79 Reviewed-on: https://chromium-review.googlesource.com/c/1322875 Commit-Queue: Camille Lamy <clamy@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#606058}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/398f37a2e0e6..c06a35b90214 git log 398f37a2e0e6..c06a35b90214 --date=short --no-merges --format='%ad %ae %s' 2018-11-07 jbolz@nvidia.com Rename PCH macro to spvtools_pch to avoid conflicts with other projects. Also add pch to test/opt. (#2034) 2018-11-06 stevenperron@google.com Validate the id bound. (#2031) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@c06a35b90214 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-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. TBR=dsinclair@chromium.org Change-Id: Ib0b2f79c6a5520b0bd4bb1498f7fe13b8adc247c Reviewed-on: https://chromium-review.googlesource.com/c/1323231Reviewed-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@{#606057}
-
Ryan Sturm authored
This CL adds a redirect PreviewsState evaluation for all PreviewsStates that are not used in a URLLoader. Specifically, Offline, server LoFi, and DRP HTTP Lite Page are not re-evaluated on a redirect, but all other Preview types are re-evaluated entirely. Bug: 892253 Change-Id: If83642658304650b29d01ac727911a9cc75dcbf1 Reviewed-on: https://chromium-review.googlesource.com/c/1308768Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#606056}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/3ca5cecde5b0..134e0525ddad git log 3ca5cecde5b0..134e0525ddad --date=short --no-merges --format='%ad %ae %s' 2018-11-07 rsavitski@google.com Kokoro CI: add build configuration for ui-clang-debug. Created with: gclient setdep -r src/third_party/perfetto@134e0525ddad The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com Change-Id: Ic307725477cd86c5f8f6f576f5cd8880fae14f79 Reviewed-on: https://chromium-review.googlesource.com/c/1323129Reviewed-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@{#606055}
-
Stephane Zermatten authored
Starting with https://chromium-review.googlesource.com/c/1319670 starting a script deletes the BatchElementChecker. Before this patch, this caused a crash when autostarting, because - BatchElementChecker calls the try_done callback set by the script_tracker - that callback autostarts a script - autostarting deletes the calling BatchElementChecker The crash happens right after calling try_done, when trying to access this to schedule a delayed task. With this patch, the callback is called after scheduling the delayed task. This way, there's no necessary usage of this after try_done is called. The weak pointer keeps track of dealing with the fact that the delayed task must not run. Bug: 806868 Change-Id: I1b907fcc96aecb66fc0b68fe2ea0f50532542100 Reviewed-on: https://chromium-review.googlesource.com/c/1323072 Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#606054}
-
Justin Cohen authored
Change-Id: If0b97a63239476ed2bb9c5ee9fdf87007f29c36c Reviewed-on: https://chromium-review.googlesource.com/c/1322389Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Danyao Wang <danyao@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#606053}
-
Takuto Ikuta authored
To speed up build time on windows component build, I will enable newly added /Zc:dllexportInlines- flag. The flag is similar to -fvisibility-inlines-hidden in gcc/clang. This flag makes inline member function is not exported if it does not have static local variables. But in few classes of chromium, we need to add additional EXPORT specifier to prevent link failure. This is a part of effort adding EXPORT speicifer to enable the flag. Master CL is https://chromium-review.googlesource.com/c/chromium/src/+/1317069 This CL was uploaded by git cl split. R=ericrk@chromium.org Bug: 901709 Change-Id: Id41759fbb8b2234c24dbaea33fcc3eff2a97b593 Reviewed-on: https://chromium-review.googlesource.com/c/1322254Reviewed-by:
Eric Karl <ericrk@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#606052}
-
Jesse McKenna authored
TaskScheduler: Add UniversalPredecessorSchedulerLock, which allows one subsequent acquisition of any SchedulerLock Bug: 889029 Change-Id: I704dfd3d463c045d919d9d57cd486ad0a8b7cf83 Reviewed-on: https://chromium-review.googlesource.com/c/1320650Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Jesse McKenna <jessemckenna@google.com> Cr-Commit-Position: refs/heads/master@{#606051}
-
Antonio Gomes authored
This is a follow up of blundell@ request in [0]. It brings no functionality, but eliminates the need of UserCloudPolicyTokenForwarder to directly inherit from IdentityManager::Observer. [0] https://crrev.com/c/1299313/3/chrome/browser/chromeos/policy/user_cloud_policy_token_forwarder.cc#78 For completeness, this CL is a 4/n CL that migrates UserCloudPolicyTokenForwarder to IdentityManager. Previous two CLs were [1], [2] and [3]. [1] https://crrev.com/c/1296873 [2] https://crrev.com/c/1298775 [3] https://crrev.com/c/1299313. It also takes the opportunity to convert the use of OAuth2TokenService::ScopeSet to Identity::ScopeSet (driven-by). BUG=893504,899175 Change-Id: I907520ed211debe3fbd1a4c21b341da4b0a81dd8 Reviewed-on: https://chromium-review.googlesource.com/c/1319770Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#606050}
-
Colin Blundell authored
As suggested by msarda@ on https://chromium-review.googlesource.com/c/chromium/src/+/1317915. TBR=jochen@chromium.org Bug: 901859 Change-Id: I4b317bafa5e4a1a017e1977e2ddd444c61c3cfd3 Reviewed-on: https://chromium-review.googlesource.com/c/1319596 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#606049}
-
Matthew Cary authored
Google.com may show a location-usage permission dialog which interferes with page interaction during profiling and may even cause chrome to crash. Wikipedia is more benign, even if it doesn't exercise the javascript and other processing that Google search result page does. Bug: 898979 Change-Id: I8f48f49ac58162bab482615f843651fafcaa9c0f Reviewed-on: https://chromium-review.googlesource.com/c/1317917Reviewed-by:
Egor Pasko <pasko@chromium.org> Commit-Queue: Matthew Cary <mattcary@chromium.org> Cr-Commit-Position: refs/heads/master@{#606048}
-
Justin Cohen authored
WKWebView -takeSnapshotWithConfiguration can return a nil UIImage if there is an error. Change-Id: Ifb1de97f9afed7436b5fae655ac9a35facdc2868 Reviewed-on: https://chromium-review.googlesource.com/c/1316750Reviewed-by:
edchin <edchin@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#606047}
-
Colin Blundell authored
//components/signin/core/browser contains three different types of code: 1. Code that forms the guts of IdentityManager and will form the guts of the Identity Service implementation (e.g., SigninManager). 2. Code that will be clients of IdentityManager (e.g., SigninTracker). 3. Code that will be used on both sides (e.g., AccountInfo). Currently, the test support for all of these is naturally grouped in the same GN target, since there was never any distinction between them. However, we need to separate this test support in GN now, as the test support for IdentityManager should depend only on 1 and 3 (and their associated test support). This CL performs an initial split, via the following process: - Moved fake_signin_manager.*, fake_profile_oauth2_token_service.*, and fake_gaia_cookie_manager_service.* into a new "test_support_internals" target that the existing target now depends on. - Kept moving in code (and adding dependencies as needed) until "gn check" no longer complained about the "test_support_internals" target including code that wasn't in any dependencies. This CL also modifies //services/identity/public/cpp:test_support to depend only on //components/signin/core/browser:internals_test_support; this change is is the concrete benefit from doing the split. Finally, this CL strips both the test_support_internals and the test_support target down to the dependencies that they actually need; this change necessitated added some missing direct dependencies to other targets. Bug: 901859 Change-Id: I0ac61f69c0c897d97b570c16d06f0e4f5f99d037 Reviewed-on: https://chromium-review.googlesource.com/c/1319669 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#606046}
-
Luna Lu authored
Bug: 829921 Change-Id: Ia2c70c62d4a4235b21996bbd185746080e1efa35 Reviewed-on: https://chromium-review.googlesource.com/c/1320010Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Luna Lu <loonybear@chromium.org> Cr-Commit-Position: refs/heads/master@{#606045}
-
Vadym Doroshenko authored
MSAN started complaining on uninitializing this variable (the first fail https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20ChromiumOS%20MSan%20Tests/9484). Probably the immediate culprit is https://chromium-review.googlesource.com/c/1320027, but it's hard to say. Anyway this issue was earlier and it's easier to fix it, by initializing it to null then revert the CL. TBR=dtseng@chromium.org TBR=dmazzoni@chromium.org Change-Id: Ie045adfcf6860b47c8e649432c6b6c6abf2061b4 Reviewed-on: https://chromium-review.googlesource.com/c/1323090Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#606044}
-
Mark Cogan authored
The CL removes a method that was functionally a no-op. Change-Id: I721a3f573253df4728dd9cc18ff484c56b52488a Reviewed-on: https://chromium-review.googlesource.com/c/1317860 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#606043}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/add61bdaac69..aced3af1656c Created with: gclient setdep -r src-internal@aced3af1656c 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: Idf2d018263fe823b73d57e5faf02ef3a76ece6f8 Reviewed-on: https://chromium-review.googlesource.com/c/1323169Reviewed-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@{#606042}
-
Vadym Doroshenko authored
Sometimes sites change forms after adding them. For example removing/ adding fields. This CL makes NewPasswordFormManager process this situation, by updating |observed_form|, parsing it again and sending new data to the renderer. Bug: 895411, 831123, 895788 Change-Id: I296180c5b30f879a3f9bcc7af7cccb98f5fa8eb8 Reviewed-on: https://chromium-review.googlesource.com/c/1317893 Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Vaclav Brozek <vabr@chromium.org> Cr-Commit-Position: refs/heads/master@{#606041}
-
Takuto Ikuta authored
To speed up build time on windows component build, I will enable newly added /Zc:dllexportInlines- flag. The flag is similar to -fvisibility-inlines-hidden in gcc/clang. This flag makes inline member function is not exported if it does not have static local variables. But in few classes of chromium, we need to add additional EXPORT specifier to prevent link failure. This is a part of effort adding EXPORT speicifer to enable the flag. Master CL is https://chromium-review.googlesource.com/c/chromium/src/+/1317069 This CL was uploaded by git cl split. R=fmalita@chromium.org Bug: 901709 Change-Id: I32a755124e41532ceebc67900047ccb4580de9c2 Reviewed-on: https://chromium-review.googlesource.com/c/1322331Reviewed-by:
Florin Malita <fmalita@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#606040}
-
Jason Chase authored
The ExperimentalProductivityFeatures flag, with a corresponding chrome flag, was intended as an easy way for developers to turn on the Feature Policy bits. The Feature Policy reporting functionality and JS API have separate runtime flags. This CL configures an implied_by relationship, so that reporting and the JS API can be turned on together with other Feature Policy functionality. Bug: 899366 Change-Id: I2ff6ac9ed48902e7d1383ace94828f9e5154a27e Reviewed-on: https://chromium-review.googlesource.com/c/1303038Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Commit-Queue: Jason Chase <chasej@chromium.org> Cr-Commit-Position: refs/heads/master@{#606039}
-
Patrik Höglund authored
The tests are clearly broken on Windows if a webcam is plugged in. They pass on win10 but only because they're disabled there. See bug for example breakages on Windows. Bug: 893494 Change-Id: I8ea43cc4e3ef23082246ff23ec635f2ec5bfbbe2 Reviewed-on: https://chromium-review.googlesource.com/c/1309789Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Patrik Höglund <phoglund@chromium.org> Cr-Commit-Position: refs/heads/master@{#606038}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/67f5c0ceac22..273fa2f3bd0b git log 67f5c0ceac22..273fa2f3bd0b --date=short --no-merges --format='%ad %ae %s' 2018-11-07 recipe-roller@chromium.org Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@273fa2f3bd0b 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-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;master.tryserver.blink:linux_trusty_blink_rel TBR=allanmac@chromium.org Change-Id: I45336359f6589fa969824646b01cd8a29a630009 Reviewed-on: https://chromium-review.googlesource.com/c/1323010Reviewed-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@{#606037}
-
Arthur Sonzogni authored
After a cross process navigation, the old RenderFrameHostImpl is kept alive the time needed for executing its unload handler. This CL generalize this by also keeping its subframes alive. This fixes unload handler not always being run. RenderFrameHostImpl is now delete as soon as: * All of its children have been deleted. * In case of an unload handler, wait FrameHostMsg_Detach. Explainer: https://goo.gl/85KSff Bug: 609963 Change-Id: Ie5b5585e54b9d1740798d649fcfac5dd2666920f Reviewed-on: https://chromium-review.googlesource.com/c/1122629 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#606036}
-
Christopher Grant authored
This change is credited to digit@, who included this cleanup in a prototype reference CL. I'm cleaning it up and landing it. Refactor common shared_library() declarations for libchrome.so, libchromefortest.so and libmonochrome.so into a shared template. BUG= Change-Id: Ie0c2005c04a664de1cf24e3536aa8b02d745f75d Reviewed-on: https://chromium-review.googlesource.com/c/1318432 Commit-Queue: Christopher Grant <cjgrant@chromium.org> Reviewed-by:
David Turner <digit@chromium.org> Reviewed-by:
agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#606035}
-
Takuto Ikuta authored
To speed up build time on windows component build, I will enable newly added /Zc:dllexportInlines- flag. The flag is similar to -fvisibility-inlines-hidden in gcc/clang. This flag makes inline member function is not exported if it does not have static local variables. But in few classes of chromium, we need to add additional EXPORT specifier to prevent link failure. This is a part of effort adding EXPORT speicifer to enable the flag. Master CL is https://chromium-review.googlesource.com/c/chromium/src/+/1317069 This CL was uploaded by git cl split. R=schenney@chromium.org Bug: 901709 Change-Id: I605f83511671f07dbf464fa1fd151954d6068da1 Reviewed-on: https://chromium-review.googlesource.com/c/1322332Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#606034}
-
Alexander Timin authored
- Do not allow assigning MessageLoop to MessageLoopCurrent. - Remove hash operator from MessageLoopCurrent. R=alexclarke@chromium.org,gab@chromium.org TBR=gab@chromium.org BUG=891670 Change-Id: If558357328d1b07abaa5ccf7bcba5f9ef3609531 Reviewed-on: https://chromium-review.googlesource.com/c/1322874Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Commit-Queue: Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#606033}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/8770ce70746a..a7f77a7c05b5 git log 8770ce70746a..a7f77a7c05b5 --date=short --no-merges --format='%ad %ae %s' 2018-11-07 alessiob@webrtc.org Isolating APM API build target: making :api an actual target. 2018-11-07 sprang@webrtc.org Update ObjCVideoEncoder to use GetEncoderInfo() 2018-11-07 nisse@webrtc.org Reland "Delete rtc::Pathname" 2018-11-07 perkj@webrtc.org Add counter to the end of FakeEncoder frames in order to make them unique. 2018-11-07 nisse@webrtc.org Add default constructor for rtc::Event 2018-11-07 qingsi@webrtc.org Resolve the race condition between mDNS name registration and Created with: gclient setdep -r src/third_party/webrtc@a7f77a7c05b5 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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ibb7c3f8a436ffa9057bf780107cb6da0e6016cd3 Reviewed-on: https://chromium-review.googlesource.com/c/1322929Reviewed-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@{#606032}
-
Clemens Arbesser authored
Bug: 806868 Change-Id: I24dbe28166fe9b1ff0193409df45cf9bfd7c7d97 Reviewed-on: https://chromium-review.googlesource.com/c/1322829Reviewed-by:
Stephane Zermatten <szermatt@chromium.org> Commit-Queue: Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#606031}
-
Eric Karl authored
Adds begin/end functions to the GL command buffer for shared image access. Currently, begin/end is a no-op in all SharedImageRepresentations, this will be fixed up in a follow up. This change just adds the commands and parameter validation in the validating and passthrough command decoders. Bug: 891059 Change-Id: Idb4bd900fa56bd470ad44ad955267e76860792cd Reviewed-on: https://chromium-review.googlesource.com/c/1313668 Commit-Queue: Eric Karl <ericrk@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#606030}
-
Christian Dullweber authored
Lots of deletion code supports a nullable filter but we pass a proper filter even when there is an empty blacklist. To avoid checking the empty filter for every type of data we should just pass a nullable filter. Change-Id: I2a580e17f3b8e18a4a1181705907abea2617b6d3 Reviewed-on: https://chromium-review.googlesource.com/c/1322769 Commit-Queue: Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#606029}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0fc9f7540077..add61bdaac69 Created with: gclient setdep -r src-internal@add61bdaac69 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: I62b8b88d50abc8f6365da5c2d10ce1081424e2e3 Reviewed-on: https://chromium-review.googlesource.com/c/1322930Reviewed-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@{#606028}
-
Vasilii Sukhanov authored
The flag was used only in the tests and had a dedicated production code. Bug: 845458 Change-Id: I27265ad5a69eecb31663b5fb1526c696f1b35d3d Reviewed-on: https://chromium-review.googlesource.com/c/1322831Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#606027}
-
Rayan Kanso authored
Few more minor changes that didn't make it in cr/1297412. Bug: 850512 Change-Id: I7a1070135aa4d10a238c8c12fd4a95ffeac34343 Reviewed-on: https://chromium-review.googlesource.com/c/1320130 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#606026}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5c8d3e17aba1..67f5c0ceac22 git log 5c8d3e17aba1..67f5c0ceac22 --date=short --no-merges --format='%ad %ae %s' 2018-11-07 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update go_deps asset 2018-11-07 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 6e8ec338eb25..825d344daa31 (1 commits) 2018-11-07 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2018-11-07 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 77b2436e28f4..1bf18ce9e2ca (2 commits) 2018-11-07 caryclark@skia.org fix paint docs 2018-11-07 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2018-11-07 mtklein@google.com remove SkScalarFastInvert Created with: gclient setdep -r src/third_party/skia@67f5c0ceac22 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-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;master.tryserver.blink:linux_trusty_blink_rel TBR=allanmac@chromium.org Change-Id: I97247d038e1401a8fcf85457942ae47c77755515 Reviewed-on: https://chromium-review.googlesource.com/c/1322314Reviewed-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@{#606025}
-
Sam McNally authored
For the first DriveFS, mount, mount_start_ is retained across mount attempts to record the total time taken to launch. When the DriveFS mount fails while offline, retries are delayed until online again. If a retry for the first launch is delayed in this fashion, the original start time is retained, causing spurious long first mount time metrics to be reported. Avoid this by clearing mount_start_ when delaying retries due to being offline. Clear it when disabling drive too. Bug: 892524 Change-Id: I47db55ca5b17965267ef813e2e70b7f7d90b662a Reviewed-on: https://chromium-review.googlesource.com/c/1322345Reviewed-by:
Sergei Datsenko <dats@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#606024}
-