- 03 Aug, 2018 40 commits
 - 
- 
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/51da39f993c8..fb6f97363738 git log 51da39f993c8..fb6f97363738 --date=short --no-merges --format='%ad %ae %s' 2018-08-03 athilenius@google.com Move betty-inremental from baremetal to GCE Created with: gclient setdep -r src/third_party/chromite@fb6f97363738 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: I335c7bd1d8f34d162f090a59117949b17a3c6e0b Reviewed-on: https://chromium-review.googlesource.com/1162383Reviewed-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@{#580627}
 - 
Jennifer Apacible authored
The WM_SIZING message is now handled by HWNDMessageHandler. When the aspect ratio is set for a window on Windows OS, the handler will adjust the final RECT bounds to adhere to the given aspect ratio. Bug: 853276 Change-Id: I54099581012d3f59e3d0535ed1285a25bb512cd9 Reviewed-on: https://chromium-review.googlesource.com/1136226 Commit-Queue: apacible <apacible@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#580626}
 - 
Jian Li authored
Launch bug: 863984 Bug: 865140 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: I021aa78fd002dc74a8c9965afce1906bdff7acdb Reviewed-on: https://chromium-review.googlesource.com/1161217 Commit-Queue: Jian Li <jianli@chromium.org> Reviewed-by:
Mathieu Perreault <mathp@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#580625}
 - 
Bence Béky authored
Modify ownership model of |int64_t* start| in PartialData::ShouldValidateCache() and PartialData::GetAvailableRangeCompleted(). Previously ownership was passed into a callback, which outlived the GetAvailableRange() call. However, when using a CompletionOnceCallback, that is destroyed as soon as GetAvailableRange() returns asynchronously, so a different ownership model is needed for |start| to provide the same lifetime guarantee. Bug: 807724 Change-Id: Ibd4bae1be23d6570618d2abdb93e398cd97c35e6 Reviewed-on: https://chromium-review.googlesource.com/1161963Reviewed-by:
Eric Roman <eroman@chromium.org> Commit-Queue: Bence Béky <bnc@chromium.org> Cr-Commit-Position: refs/heads/master@{#580624}
 - 
John Abd-El-Malek authored
This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/1156566 with fixes in the fake test class for Mac debug flake in 2 tests. TBR=nasko Bug: 800212 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_mojo;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: If3e60cba6c6d501855b0197d891aea4c769a4361 Reviewed-on: https://chromium-review.googlesource.com/1162263 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#580623}
 - 
Gabriel Charette authored
[TaskScheduler] Forward all public TaskScheduler headers to forwarding headers in preparation for source move Core move CL : https://chromium-review.googlesource.com/c/chromium/src/+/1161088 Move strategy : 1) Rebase this CL on ToT and mass migrate all callers of public base/task_scheduler headers to their matching *_forward.h header. 2) Land core move CL 3) Mass migrate away from *_forward.h headers in https://chromium-review.googlesource.com/c/chromium/src/+/1161116 This move strategy was chosen to keep as much git history as possible in (2). See code comments on forward headers for details. Once this CL and its follow-ups are approved, I will sync it to top-of-tree, mass migrate all existing users of these headers to their *_forward.h version in this CL (TBR'ed) and follow-up with the other two swiftly back-to-back. TBR=robliao@chromium.org (for mass migration of existing callers) Bug: 867421 Change-Id: Iea684e022181c0611abe7f92629599afc369822b Reviewed-on: https://chromium-review.googlesource.com/1161179 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#580622}
 - 
Amy Qiu authored
Since it's been a week after refreshing pathological_mobile_sites, remove the old pages. Bug: 852530 Change-Id: I75096a10510f8d9bec5838deeb6dcd00e0c55fc0 Reviewed-on: https://chromium-review.googlesource.com/1162344Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Amy Qiu <amyqiu@google.com> Cr-Commit-Position: refs/heads/master@{#580621}
 - 
Xiaohan Wang authored
The EME spec requires the order of some events. For example, after update() [1], we should "run the Update Expiration algorithm on the session, providing expiration time", then "resolve promise with true". The former is part of the ContentDecryptionModuleClient interface, while the latter is a callback on the ContentDecryptionModule interface. To preserve the order, this CL uses associated interface [2] to ensure message ordering. [1] https://w3c.github.io/encrypted-media/#dom-mediakeysession-update [2] //src/mojo/public/cpp/bindings/README.md#Associated-Interfaces Bug: 869550 Test: CDM_10/ECKEncryptedMediaTest.MessageTypeTest/0 working, see Bug Change-Id: I1afd1657581f83347235357fb26972a6ba657f1c Reviewed-on: https://chromium-review.googlesource.com/1162309Reviewed-by:
Frank Liberato <liberato@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#580620}
 - 
Alexis Hetu authored
The gl renderer for all chromium tests was recently changed from OSMesa to SwiftShader. OSMesa offers a synchronous API to OpenGL, while SwiftShader is asynchronous (draw calls are received and yield before the drawing operation is complete, letting chromium resume its execution). Because of this it seems like the affected MacOS tests here can become idle while rendering is happening in the background, causing the tests to fail. To solve this, we need to actually wait for drawing to be completed, rather than waiting for an idle period, in order to resume the test. Doing this allows these tests to pass. R=ccameron@chromium.org Bug: chromium:870465 Change-Id: I6f1555b93a83d80b06e72b3a469c01dde44e1312 Reviewed-on: https://chromium-review.googlesource.com/1162350 Commit-Queue: Alexis Hétu <sugoi@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#580619}
 - 
Yue Li authored
Bug: None Test: Manual Test Change-Id: Ia0ab2867db8b047049534632d4ffdbc6e618ce56 Reviewed-on: https://chromium-review.googlesource.com/1162508Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Yue Li <updowndota@chromium.org> Cr-Commit-Position: refs/heads/master@{#580618}
 - 
Chris Lu authored
ApplicationCommands conforms to BrowsingDataCommands, but we need to explicitly dispatch them still. Change-Id: I02dbf849677c7391a6a123917f7773d2330be003 Reviewed-on: https://chromium-review.googlesource.com/1162279Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Cr-Commit-Position: refs/heads/master@{#580617}
 - 
Bruce Dawson authored
test_process.exe was being linked with /SUBSYSTEM:CONSOLE, despite being a windowed app with a wWinMain entry point. With lld-link.exe this seems to work fine, suggesting that lld ignores the/SUBSYSTEM flag. lld-link may change this behavior (https://bugs.llvm.org/show_bug.cgi?id=38397) so it seems worthwhile to fix the build flags for this executable. Doing so will also be less confusing. Bug: 869503 Change-Id: I52a61aab678fa135f3da8c10bc82a4cdf649b5ae Reviewed-on: https://chromium-review.googlesource.com/1157656 Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Reviewed-by:
Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#580616}
 - 
Peter Kasting authored
This provides a consistent alignment point for theme authors, makes some themes (e.g. Dots) look correct (other themes want other values, e.g. 0, so there's no one "right way" here), and prevents mirroring above the top of the frame image in Refresh, since no mode has a frame height above the tabs > 16 DIP. Bug: 866671 Change-Id: I1d79627e2735d54a332013ee70a2c71f107a898f Reviewed-on: https://chromium-review.googlesource.com/1157878 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#580615}
 - 
Christian Fremerey authored
The logic deciding if the service is enabled and if it is to be run in the Browser process or a dedicated utility process is currently distributed in two methods each returning boolean. These two methods are never supposed to both return true. To make this more clear and avoid it from happening in future changes, use an internal enum. Bug: 721812, 870819 Change-Id: I32572dca80d1a687e0b292c26e1364d6d01d3585 Reviewed-on: https://chromium-review.googlesource.com/1162434 Commit-Queue: Christian Fremerey <chfremer@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#580614}
 - 
Emircan Uysaler authored
This CL completes a TODO in media_stream_controls.h, by switching from std::string to MediaStreamType. Accordingly, it changes related mojo files, renderer side UserMediaProcessor and browser side MediaStreamManager. This will let us add new MediaStreamTypes for request in follow-up CLs. Bug: 326740 Change-Id: I13e2613c190d342c95f084b3a06933a9458a12a8 Reviewed-on: https://chromium-review.googlesource.com/1159839Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Christian Fremerey <chfremer@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Emircan Uysaler <emircan@chromium.org> Cr-Commit-Position: refs/heads/master@{#580613}
 - 
Kevin Schoedel authored
This is a step toward congruence between touch exploration on cast and cast system gesture handling. TouchExplorationManager can be persistently installed as an EventRewriter, avoiding the problem of TouchExplorationController appearing too late in the chain. Also removes some dead code. Bug: b/112073644 Test: manual Change-Id: I29b20c880c3fccce413f2f2ace981899cdcb9f9b Reviewed-on: https://chromium-review.googlesource.com/1160876 Commit-Queue: Kevin Schoedel <kpschoedel@chromium.org> Reviewed-by:
Alex Sakhartchouk <alexst@chromium.org> Cr-Commit-Position: refs/heads/master@{#580612}
 - 
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/f6027ed1df0b..27928c385ec6 git log f6027ed1df0b..27928c385ec6 --date=short --no-merges --format='%ad %ae %s' 2018-08-03 wangge@google.com Add Failback for `chrome.gpuBenchmarking.pageScaleFactor` Created with: gclient setdep -r src/third_party/catapult@27928c385ec6 The AutoRoll server is located here: https://catapult-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=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:866881 TBR=sullivan@chromium.org Change-Id: Id597e4f161e9c44b79c86132ee408695fd4c6d7c Reviewed-on: https://chromium-review.googlesource.com/1162382Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#580611}
 - 
Piotr Pawliczek authored
Inside the method mentioned above we were not able to distinguish between manual and automatic printer installation. As a result in both cases the event metrics::PrinterEventProto::SETUP_MANUAL was reported and the event metrics::PrinterEventProto::SETUP_AUTOMATIC has never appeared in logs. To solve this problem I have added bool parameter is_automatic to the method that carries information about a type of printer installation. It allows to distinguish between these two cases and report a correct event. BUG=chromium:829542 TEST=tested manually on nautilus chrombook Change-Id: I8d1f3bf70b9b218a734726f2fb1b8ab2af537184 Reviewed-on: https://chromium-review.googlesource.com/1161099Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Reviewed-by:
Luis Hector Chavez <lhchavez@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Piotr Pawliczek <pawliczek@chromium.org> Cr-Commit-Position: refs/heads/master@{#580610}
 - 
bsheedy authored
Only updates the VR controller's previous button states if the controller is connected. This fixes some flakiness with VR tests caused by the controller briefly disconnecting then reconnecting. Bug: 870031 Change-Id: If1e0e8807120e9ddba94c05b651ae553b1e4f60b Reviewed-on: https://chromium-review.googlesource.com/1159273Reviewed-by:
Aldo Culquicondor <acondor@chromium.org> Reviewed-by:
Amirhossein Simjour <asimjour@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#580609}
 - 
Kyle Horimoto authored
The MultiDeviceSetup service is now responsible for owning these preferences. See go/cros-multidevice-prefs for details. Bug: 824568 Change-Id: I14fe45058585c00087d1aed88392c451bc79a6ed Reviewed-on: https://chromium-review.googlesource.com/1161337 Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#580608}
 - 
Theresa authored
BUG=869688 Change-Id: I3d42473540556fde6b39ff3fc6d16127ed33ca3e Reviewed-on: https://chromium-review.googlesource.com/1162435Reviewed-by:
Becky Zhou <huayinz@chromium.org> Commit-Queue: Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#580607}
 - 
Fredrik Hubinette authored
Bug: 647725 Change-Id: I8c5ca15c75e2a0114a39f6eed64fec5fbd863b7c Reviewed-on: https://chromium-review.googlesource.com/1161321Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Fredrik Hubinette <hubbe@chromium.org> Cr-Commit-Position: refs/heads/master@{#580606}
 - 
David Black authored
The motion spec dictates that the stage should not be cleared when a new query is committed. Instead, the previous query response should fade out while we wait for the next response to come in (which should also be animated). This CL does not implement the entire motion spec, only the portion that fades out the previous query response while we are waiting for the next response to arrive. Changes are guarded behind kIsMotionSpecEnabled. See bug for spec/demo. Bug: b:112091713 Change-Id: I88cb4703f8b8b697ce87ac5a70162853d8826244 Reviewed-on: https://chromium-review.googlesource.com/1159223Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: David Black <dmblack@google.com> Cr-Commit-Position: refs/heads/master@{#580605}
 - 
Wez authored
Migrate the net::NetworkChangeNotifier implementation for Fuchsia off of using the deprecated fuchsia::netstack::NotificationListener to receive network interface change events, to use the OnInterfacesChanged event on the netstack::Netstack interface, instead. TBR=eroman Change-Id: I492a05209a27a6c5d41220b82b6bcd07dae407eb Reviewed-on: https://chromium-review.googlesource.com/1162305Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#580604}
 - 
Michael Thiessen authored
Now that all VR code is behind the VR module, the VrClassesWrapper and a bunch of other interfaces are redundant. TBR=yfriedman@chromium.org Bug: 862639 Change-Id: I52d10c319a255515469414346c4f3730084bd617 Reviewed-on: https://chromium-review.googlesource.com/1161110Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#580603}
 - 
Artur Khachatryan authored
Change-Id: I247dd746fd2e559d8e2d752ff7878e68fb54846f Reviewed-on: https://chromium-review.googlesource.com/1162501Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Artur Khachatryan <khachatryan@chromium.org> Cr-Commit-Position: refs/heads/master@{#580602}
 - 
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/0ecae0ae..12c70426 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;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I6cd8703cf3635fc5a5c1cb984de0b57c16e25c2b Reviewed-on: https://chromium-review.googlesource.com/1162307Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#580601}
 - 
Chromium WPT Sync authored
Using wpt-import in Chromium 0856d23e. With Chromium commits locally applied on WPT: 7dad0f17 "Added new Sec-Metadata Web Platform Tests." Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22272 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: worker-dev@chromium.org: external/wpt/workers TBR=foolip No-Export: true Change-Id: I7c4b226374d3e80ccccef3f2a4c3a0e35b6a4476 Reviewed-on: https://chromium-review.googlesource.com/1162273 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#580600}
 - 
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/f5cf02ac2c4a..d54f5f5c763c git log f5cf02ac2c4a..d54f5f5c763c --date=short --no-merges --format='%ad %ae %s' 2018-08-03 sakal@webrtc.org Rename rtc_instrumentation_test_apk targets to end with _test_apk. 2018-08-03 magjed@webrtc.org Android: Remove custom matrix helper functions in RendererCommon 2018-08-03 mbonadei@webrtc.org Remove definition of FEATURE_ENABLE_VOICEMAIL, FEATURE_ENABLE_PSTN. 2018-08-03 philipel@webrtc.org Reland "Remove RTPVideoHeader::h264() accessors." 2018-08-03 oprypin@webrtc.org JNI generation: Replace base::subtle::AtomicWord with std::atomic<> 2018-08-03 buildbot@webrtc.org Roll chromium_revision 4dd959af..06e87fb3 (579686:580149) 2018-08-03 oprypin@webrtc.org Don't allocate an array of size 0, it causes a UBSan failure 2018-08-03 kthelgason@webrtc.org Remove dead code. 2018-08-02 zstein@webrtc.org Add AsyncResolverFactory interface and basic implementation. 2018-08-02 srte@webrtc.org Always sends probes when they are generated. 2018-08-02 nisse@webrtc.org Delete class TelephoneEventHandler and related code. 2018-08-02 kthelgason@webrtc.org Fix occasional crash in iOS ADM. 2018-08-02 nisse@webrtc.org Delete telephone-event handling from RTPReceiverAudio. 2018-08-02 oprypin@webrtc.org Fix a warning about comparison of integers of different signs 2018-08-02 philipel@webrtc.org Add members for the codec agnostic descriptor to RTPVideoHeader. 2018-08-02 sakal@webrtc.org Delete MockRenderer and replace it with identical MockSink class. Created with: gclient setdep -r src/third_party/webrtc@d54f5f5c763c 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=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng BUG=chromium:none,chromium:867475,chromium:None,chromium:868776,chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: If94dce305aee0c40ca6d1f33f6b41d966662affe Reviewed-on: https://chromium-review.googlesource.com/1162105Reviewed-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@{#580599}
 - 
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/7d0339950377..b33f9ebe9057 git log 7d0339950377..b33f9ebe9057 --date=short --no-merges --format='%ad %ae %s' 2018-08-03 borenet@google.com [infra] Update vpython CIPD package 2018-08-03 kjlubick@google.com Add job for building PathKit to WASM using Docker 2018-08-03 timliang@google.com validate GrMtlBuffer after forcing it to be static 2018-08-03 brianosman@google.com Avoid coverage bleed for AA arcs with tiny sweep angles 2018-08-03 jvanverth@google.com Revert "Hoist path check" 2018-08-03 bsalomon@google.com Make fixed dynamic states be conditionally allocated 2018-08-03 rmistry@google.com Revert "Disable bookmaker CLs automatic CQ+2 for now" Created with: gclient setdep -r src/third_party/skia@b33f9ebe9057 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;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:b/112018278 TBR=scroggo@chromium.org Change-Id: Ia94bc367429863fbd1096aadaa88f1303d1486f0 Reviewed-on: https://chromium-review.googlesource.com/1162111Reviewed-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@{#580598}
 - 
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/ee09b25fcad3..51da39f993c8 git log ee09b25fcad3..51da39f993c8 --date=short --no-merges --format='%ad %ae %s' 2018-08-03 vapier@chromium.org upload_gce_image: drop 2018-08-03 vapier@chromium.org cros_collections: split out collections related logic to a new module 2018-08-03 lannm@chromium.org cbuildbot: Remove UpdateGitRepo 2018-08-03 lannm@chromium.org cbuildbot: Remove CanaryCompletionStage._ComposeTreeStatusMessage 2018-08-03 lannm@chromium.org cbuildbot: Remove PrepManifestForRepo 2018-08-03 vapier@chromium.org gs: update to 4.33 2018-08-03 derat@chromium.org chromeos_config: Add bvt-tast-{android,chrome}-pfq. Created with: gclient setdep -r src/third_party/chromite@51da39f993c8 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: I58983b99110688ab017f5b66fa9b7bdce46d1571 Reviewed-on: https://chromium-review.googlesource.com/1161151Reviewed-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@{#580597}
 - 
Amy Qiu authored
Now that it's been a week since key_desktop_move_cases was refreshed, remove the old pages. Bug: 852530 Change-Id: Ic439646390d3acafc9d59f26a089e7ca94fc2466 Reviewed-on: https://chromium-review.googlesource.com/1162341Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Amy Qiu <amyqiu@google.com> Cr-Commit-Position: refs/heads/master@{#580596}
 - 
Clark DuVall authored
This is a reland of db560919 Reland disables flaky ExtensionWebRequestApiTest.WebRequestTestOSDD on Windows. Original change's description: > Fixes ExtensionWebRequestApiTest.WebRequestBlocking with network service > > Getting this test working required a few fixes: > - Modifying a header rather than Set-Cookie for some tests, which > required switching to XMLHttpRequest (crbug.com/827582) > - Handling redirect from http:// -> chrome-extension://, and bypassing > security checks if this is from web request > - Plumbing through whether the request is async or not > > This is not handling subresource redirects because subresource > redirects to schemes other than http/https/data are not supported > yet with network service (crbug.com/868545). > > Also adds a bunch of tests for redirects. > > Bug: 721414 > Cq-Include-Trybots: luci.chromium.try:linux_mojo > Reviewed-on: https://chromium-review.googlesource.com/1145956 > Reviewed-by: Nick Carter <nick@chromium.org> > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > Reviewed-by: Reilly Grant <reillyg@chromium.org> > Commit-Queue: Clark DuVall <cduvall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#580365} TBR=nick@chromium.org,jam@chromium.org,reillyg@chromium.org,karandeepb@chromium.org Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I8c37f335c96aa8f43548e9118e96f095f2ae6362 Bug: 721414 Reviewed-on: https://chromium-review.googlesource.com/1162274 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#580595}
 - 
Fredrik Hubinette authored
We hide some network state changes when loading cross-origin videos. The idea is that non-videos will look exactly like non-existing resources. However, if preload=none, no loading is actually occuring, so there is no reason to hide the preload state. Also, since the player will not naturally progress to an error or "have metadata" stage, it will be stuck loading without this patch. Bug: 852119 Change-Id: I660b6167e1783dae79c90aa5479c504f9d302a6b Reviewed-on: https://chromium-review.googlesource.com/1149143Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Fredrik Hubinette <hubbe@chromium.org> Cr-Commit-Position: refs/heads/master@{#580594}
 - 
angle-chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/d69a5f124d9b..b8430dd749b0 git log d69a5f124d9b..b8430dd749b0 --date=short --no-merges --format='%ad %ae %s' 2018-08-03 geofflang@chromium.org Use FixedVector for storing textures referenced by a framebuffer. Created with: gclient setdep -r src/third_party/angle@b8430dd749b0 The AutoRoll server is located here: https://angle-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=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=fjhenigman@chromium.org Change-Id: I462a6809aa3ef6f83da376f2b5afdf57c827b196 Reviewed-on: https://chromium-review.googlesource.com/1162109Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#580593}
 - 
Yue Li authored
Show the notification when existring user update to M70. Bug: b/111936939 Test: Manual Test Change-Id: I46df54c1ec360aa9110b679f858d30cc665171a8 Reviewed-on: https://chromium-review.googlesource.com/1155975 Commit-Queue: Yue Li <updowndota@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#580592}
 - 
Fritz Koenig authored
Filters can use the pixels of the images they overlay. When using hardware planes the final composition is done on the display controller, so the filter doesn't have a chance to get the pixel values of the underlaying plane. BUG=chromium:854790 TEST=UnderlayTest.DisallowFilteredQuadOnTop Change-Id: Id8e7e2031343c61c1334071a368cb367c0cd5eb3 Reviewed-on: https://chromium-review.googlesource.com/1156878 Commit-Queue: Fritz Koenig <frkoenig@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#580591}
 - 
Sami Kyostila authored
TBR=altimin@chromium.org Change-Id: I9db618aee880f0d0ad2a49f581d6b7ac60f7152b Reviewed-on: https://chromium-review.googlesource.com/1162328Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#580590}
 - 
Xida Chen authored
The previous CL: https://chromium-review.googlesource.com/c/chromium/src/+/1151094 was reverted. The reason is that there were some crashes. This CL solve the problem. PS#1 is exactly the same as the previous CL which was reverted, so that it is easier for review. TBR=creis@chromium.org Bug: 851644 Change-Id: I80a8c3b7dfd94e7abace4e3281b959f9fc1dcd2a Reviewed-on: https://chromium-review.googlesource.com/1157698Reviewed-by:
Xida Chen <xidachen@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#580589}
 - 
Andrey Kosyakov authored
Change-Id: I70275386caedc3a1b2bf695b26008006b9fe023f Reviewed-on: https://chromium-review.googlesource.com/1160939Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#580588}
 
 -