- 20 Apr, 2019 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/208ff2dc446d..c4cc16e5940f git log 208ff2dc446d..c4cc16e5940f --date=short --no-merges --format='%ad %ae %s' 2019-04-20 dburger@chromium.org Remove special retry handling for nyan_blaze-paladin. Created with: gclient setdep -r src/third_party/chromite@c4cc16e5940f 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. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: Ife8af89cda740091877172079a1a79f858c3eb1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576284Reviewed-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@{#652754}
-
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: I5aac6fa150fce7cc024a5edcee0e298bf53fe9f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576286Reviewed-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@{#652753}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b01f0f1dba2a..e2fe088e15c3 Created with: gclient setdep -r src-internal@e2fe088e15c3 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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=fdoray@chromium.org,bsep@chromium.org,keishi@chromium.org,chanli@chromium.org Change-Id: I60dafa5a6fc7a4a32f37625ae97bb2d9f333e334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576324Reviewed-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@{#652752}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/be7cf0ddf8ff..d863bc2e807e git log be7cf0ddf8ff..d863bc2e807e --date=short --no-merges --format='%ad %ae %s' 2019-04-20 benjhayden@chromium.org Migrate ReportNamesRequest to es6 module Created with: gclient setdep -r src/third_party/catapult@d863bc2e807e The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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 BUG=chromium:950011 TBR=charliea@chromium.org Change-Id: I35e7355ff989887e965ddc17d8fd07aec62d5d00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576322Reviewed-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@{#652751}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/60caf55788c6..6805e5544d6c git log 60caf55788c6..6805e5544d6c --date=short --no-merges --format='%ad %ae %s' 2019-04-20 fjhenigman@users.noreply.github.com Fix Windows build uploads. (#597) Created with: gclient setdep -r src/third_party/shaderc/src@6805e5544d6c The AutoRoll server is located here: https://autoroll.skia.org/r/shaderc-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: I153074a87c6a3e751db969fff139ff3d554ad726 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576323Reviewed-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@{#652750}
-
Justin Cohen authored
This removes the kBrowserContainerContainsNTP experiment, many of the files in c/b/u/ntp, and many of the references to the old code throughout the codebase. This includes the added benefit of finally getting rid of StatusBarHeight(). Bug: 883770, 807330, 826369 Change-Id: Ic5364c243331ede4d4bb8723432319e4d95fe9a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573176 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#652749}
-
Ehsan Karamad authored
This CL adds one more bucket to MimeHandlerViewUMATypes which counts the usage of internal calls (from C++) to postMessage (used for printing). TBR=wjmaclean@chromium.org Bug: 659750 Change-Id: I08c5194012c97f0a603dd338e454b201dfafd1da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576204Reviewed-by:
Ehsan Karamad <ekaramad@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#652748}
-
Xiao Yang authored
1. Register AssistantManagerServiceImpl as a listener of libassisant media manager and notify assistant_media_session about media metadata in OnPlaybackStateChange(). 2. Implemented addObserver(), suspend() and resume() API for assistant_media_session. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome Change-Id: Ib81b9b10e1fad6e711e48b31f0703dd710ae0ba6 Bug: 130315881 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557006 Commit-Queue: Xiao Yang <yanxiao@google.com> Reviewed-by:
Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#652747}
-
Siddhartha S authored
Bug: 925142 Change-Id: I727e64485ea491d5d5ef182fa62f877a8a7a17dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575087 Commit-Queue: ssid <ssid@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#652746}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/e057820e36f5..208ff2dc446d git log e057820e36f5..208ff2dc446d --date=short --no-merges --format='%ad %ae %s' 2019-04-20 haddowk@chromium.org Revert "chromite: Remove TreeIsOpen and dependencies." Created with: gclient setdep -r src/third_party/chromite@208ff2dc446d 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. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: I6e7e009d7aae4e53021463234595e5e4c13d291f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576318Reviewed-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@{#652745}
-
Chris Blume authored
https://chromium.googlesource.com/chromium/deps/libjpeg_turbo.git/+log/61a2bbaa9aec..2de84a43e683 $ git log 61a2bbaa9..2de84a43e --date=short --no-merges --format='%ad %ae %s' 2019-04-18 cblume Pull comments from upstream 2019-04-16 cblume libjpeg_turbo: Fix GN check 2019-04-16 cblume Check maximum CPUID leaf 2019-03-04 jmadill Fix gn header check. 2019-03-01 cblume Update libjpeg-turbo to v2.0.1 This CL also updates our expected pixel results to reflect an imperceptible change in 4:4:0 decoding. This change is the result of 4:4:0 now having fancy upsampling. R=scroggo@chromium.org Bug: 922430 Change-Id: I97b3269286dd6464cb731e5ca9dad355925a3925 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496758 Commit-Queue: Chris Blume <cblume@chromium.org> Reviewed-by:
Leon Scroggins <scroggo@chromium.org> Auto-Submit: Chris Blume <cblume@chromium.org> Cr-Commit-Position: refs/heads/master@{#652744}
-
rbpotter authored
This event can cause a race condition in release build tests, since the real event can fire after the original instance of print-preview-app is removed from the DOM and the new one has been attached. This can result in multiple use-cloud-print events (one real, one test) in tests of cloud print behavior. This race condition appears to be exposed by waiting for the HTML Imports polyfill and element definition, which are necessary changes for migrating Print Preview to use the polyfill. There is also no need for a separate event now that Print Preview is using cr.sendWithPromise to handle initial settings instead of relying on chrome.send and multiple calls to CallJavascriptFunctionUnsafe, which needed to be ordered on the C++ side. Instead, we can send the cloud print URL in the initial settings if cloud print is enabled, and always set the cloud print interface before initializing the DestinationStore in JS to guarantee that autoselection of cloud printers works. Bug: 925517 Change-Id: Ifa84ef832ee8d129ab25ab5bfdb0f33882d1b48a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576120 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#652743}
-
Victor Costan authored
Bug: 953838 Change-Id: I74a3f5b2c661cdc31f5ea704961c78e465b35c74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574216 Auto-Submit: Victor Costan <pwnall@chromium.org> Reviewed-by:
Chris Mumford <cmumford@google.com> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#652742}
-
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: I76e24c027cb9f0423c88ba7856b22f3bd041006d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576319Reviewed-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@{#652741}
-
Tom Anderson authored
BUG=801780 R=thakis Change-Id: Ife6f11c4e02534c879731274d427b0f563b8fa08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556590 Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#652740}
-
chrome://fileiconDan Beam authored
Instead of using custom dir/like/things, let's use the more standard: ?param1=val1¶m2=val2 Because it allows us to use URLSearchParams[1] in JS: url.searchParams.set('param1', 'val1'); And net::QueryIterator in C++: for (net::QueryIterator it(url); !it.IsAtEnd(); it.Advance()) { // use it.GetKey() and it.GetValue() } R=dpapad@chromium.org BUG=953962 [1] https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams Change-Id: I708ae3349d826793b5d1dbd6e1c1683e08ce254e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574373 Commit-Queue: Dan Beam <dbeam@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#652739}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/d8ce95982c94..be7cf0ddf8ff git log d8ce95982c94..be7cf0ddf8ff --date=short --no-merges --format='%ad %ae %s' 2019-04-20 ntfschr@chromium.org devil: support minSdkVersion with string value Created with: gclient setdep -r src/third_party/catapult@be7cf0ddf8ff The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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 BUG=chromium:952001 TBR=charliea@chromium.org Change-Id: I1e6407099cbe3d7a9de7835d506ba621622c23a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576109Reviewed-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@{#652738}
-
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: I5a32752ca3e84a5d372071762791751ac870a769 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576235Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#652737}
-
François Beaufort authored
This CL makes sure Picture-in-Picture window is always visible on all workspaces by calling SetVisibleOnAllWorkspaces when it is shown. Bug: 954470 Change-Id: If1f60781dd79cb8fb884cb41f3fe596e77fd9438 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575598 Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#652736}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/34a4af2494cc..e057820e36f5 git log 34a4af2494cc..e057820e36f5 --date=short --no-merges --format='%ad %ae %s' 2019-04-20 evanhernandez@chromium.org chromite: Remove TreeIsOpen and dependencies. 2019-04-20 dgagnon@google.com Update gen_luci_scheduler with R75 branch 2019-04-20 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@e057820e36f5 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. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: Iff3fbb3dfd0bdce6dd21233059bd7af94904ff8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574613Reviewed-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@{#652735}
-
Sunny Sachanandani authored
Map usage STAGING texture along with copy to usage DEFAULT texture to workaround crashes when mapping usage DYNAMIC textures. Restrict workaround to Intel driver versions < 24 based on crash data. Also add a few trace events for swap buffers, texture upload, blit, etc. Bug: 890227 Change-Id: I1cc9bae3fc0ddf6303375c99054113a9a995806c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576016Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#652734}
-
Maggie Chen authored
The current way to handle the overlay swap chain creation failure might cause a complet black browser window, which is a very bad user experience. If we disable overlay when the creation fails, the video playback will be able to continue through GL composition if there is no other issue. Bug: 954661 Change-Id: I5f1355f9ff46d7c9a88a1ff0ccad4ed229710eb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576034Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Maggie Chen <magchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#652733}
-
rajendrant authored
Bug: 952435 Change-Id: I9568cc51d467feba3f20b82b60cd465d5bf3d09d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574655Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#652732}
-
Johannes Henkel authored
New Rev = 4c2d2efe9aacf50d4242290097a2e74c14229276 This brings in the Status::ToASCIIString method. Change-Id: I01e5618f03cb4105b1f7144cdc6ee8ce6f80b23b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576230Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#652731}
-
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: Icb709a41f6552b5ba6114fe0d2d825d4ee7bdcf9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574612Reviewed-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@{#652730}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/80140adf0944..b01f0f1dba2a Created with: gclient setdep -r src-internal@b01f0f1dba2a 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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=fdoray@chromium.org,bsep@chromium.org,keishi@chromium.org,chanli@chromium.org Change-Id: I7b5af9c8e435db8ff3086c5f6ff0b5bfcbee3a8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574611Reviewed-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@{#652729}
-
Bruce Dawson authored
It is possible to accidentally call the Windows GetVersion() function when base::win::GetVersion() is intended. The code would compile due to implicit conversions from enum to int. This allowed buggy code to be checked in. Using enum class makes this error impossible. This change switches enum Version to enum class Version, which includes changing every usage of the Version enum. For services\service_manager TBR=wfh@chromium.org For the rest TBR=jochen@chromium.org Bug: 946677 Change-Id: I4b446370499e5e6a24446d18b541e2b4948405e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1541594Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#652728}
-
Evan Stade authored
Ash will continue talking to the power manager daemon via DBus, while providing a mojo service that Chrome can connect to for its power manager needs. The mojo interface is only used by client code that explicitly opts in, and only when a specific feature flag is passed. This CL partially implements the Mojo interface as it's used by BrightnessMonitor, which is to say, it implements very little. Change-Id: Id0b286a690d1833b1090960cf31edfbe66124b24 Bug: 644348 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531466 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Dan Erat <derat@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#652727}
-
Kenneth Russell authored
conformance/programs/program-test.html conformance/uniforms/uniform-default-values.html These tests are passing on the upgraded Mesa driver. Bug: 928530 Bug: 927466 Change-Id: Ib2ab2bf1ac30b777931dbc9344f2e3b20c608f9c Tbr: piman@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574649Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#652726}
-
Siddhartha S authored
Writing to consumer client data pipe in main thread can cause us to wait for the pipe to be ready on main thread. The main thread need to run other work like giving out SMBs to processes. It can also cause deadlock if the consumer client is also waiting for SMB. So, move the writer to background task runner. BUG=953837 Change-Id: I5cad2c45af8b4c7f0a69372e1c2633896c7e518e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573162 Commit-Queue: ssid <ssid@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#652725}
-
Nasko Oskov authored
This check was initially added in r629679 and then reverted in r633938 due to unexpected renderer process terminations. Some bugs were discovered and fixed in the meantime, so this is an attempt to add the check back. The CL includes crash keys to capture more information about the state when the process is terminated to aid debugging. The instrumentation will be removed separately if all goes smoothly. Bug: 918565, 931895 Change-Id: I4de255731ee8251714132fdbea56777da4e4b440 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549318 Commit-Queue: Nasko Oskov <nasko@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#652724}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/5cc5a8e61949..d8ce95982c94 git log 5cc5a8e61949..d8ce95982c94 --date=short --no-merges --format='%ad %ae %s' 2019-04-19 benjhayden@chromium.org Migrate alerts-table to es6 module Created with: gclient setdep -r src/third_party/catapult@d8ce95982c94 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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 BUG=chromium:950011 TBR=charliea@chromium.org Change-Id: I378e1838dd38f166a8b72840fc3b02f033c946d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575291Reviewed-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@{#652723}
-
Yuwei Huang authored
We will introduce a new heartbeat sender that connects to the new directory server. This CL renames the old HeartbeatSender to XmppHeartbeatSender to prevent confusion. Bug: 954695 Change-Id: Ie29caedb55de0db2dd3d2e8801971c9ea015b164 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574653 Commit-Queue: Yuwei Huang <yuweih@chromium.org> Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#652722}
-
Michael Thiessen authored
No functionality changes intended here, this should just be a no-op refactor. This refactor is to make it easier to land followup changes for spatial navigation here: https://chromium-review.googlesource.com/c/chromium/src/+/1562714/ Bug: 938534 Change-Id: Ia3c2b993db9e2055f7c42f209c3806dd08c34daf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567081 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#652721}
-
Martin Kreichgauer authored
There is a specialization in SetPinRequestHandler, but nothing ever calls ProvidePIN on the base class. Bug: 870892 Change-Id: I86564915b1ae2a1d0fe7996a5e23ec8e5d10ad39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574643 Auto-Submit: Martin Kreichgauer <martinkr@google.com> Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#652720}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/0ab4b3dfabf6..34a4af2494cc git log 0ab4b3dfabf6..34a4af2494cc --date=short --no-merges --format='%ad %ae %s' 2019-04-20 derat@chromium.org chromeos_config: Run Tast tests on VM PFQ builders. Created with: gclient setdep -r src/third_party/chromite@34a4af2494cc 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. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: Ifae5ebe7da41fe53a0197fa56d80d2cfcb6eb798 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575960Reviewed-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@{#652719}
-
Harry Cutts authored
The copies in `EventConverterEvdevImplTest` and `InputInjectorEvdevTest` were exact duplicates, and I'm working on a CL that also needs it. Also renamed it to `FakeCursorDelegateEvdev`, since it doesn't log calls to its methods and so isn't really a mock. No behaviour changes should be caused by this CL. Bug: none Test: run `EventConverterEvdevImplTest` and `InputInjectorEvdevTest`. Change-Id: Iad54935e675bb2b253dcf6aa5c2bb0d9d9cae1be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559207Reviewed-by:
Michael Spang <spang@chromium.org> Commit-Queue: Harry Cutts <hcutts@chromium.org> Cr-Commit-Position: refs/heads/master@{#652718}
-
Vidal Diazleal authored
Tab titles in the devtools are not localizable, this PR makes the title function to actually use l10n tagged templates and fixes the following comment on the code: third_party\blink\renderer\devtools\front_end\Runtime.js // FIXME: should be Common.UIString() but runtime is not l10n aware yet. Change-Id: I4a651e2f1b4ef0e0e6d07b54d52e44c17aeda057 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554648 Commit-Queue: Vidal Diazleal <vidorteg@microsoft.com> Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Cr-Commit-Position: refs/heads/master@{#652717}
-
Hwanseung Lee authored
Use enum class instead of enum at MenuController enum class is more type safety. Bug: 940736 Change-Id: I9302a3d7cc5c4d4c8ffdfdbf758141ad34a417b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1569370Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com> Cr-Commit-Position: refs/heads/master@{#652716}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/990de7c7fcb5..80140adf0944 Created with: gclient setdep -r src-internal@80140adf0944 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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=fdoray@chromium.org,bsep@chromium.org,keishi@chromium.org,chanli@chromium.org Change-Id: Icaf2cdb67c9fde554d39c84c8ae9524cb4e0cd5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1576009Reviewed-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@{#652715}
-