- 01 Oct, 2018 40 commits
-
-
Fergal Daly authored
This test was using mock.py's assert_not_called method but that does not exist in the version in third_party/pymock. The result is that the assert call was mocked out, allowing the test to pass without actually testing anything. Fix is two-fold: 1 factor out the filtering code and test it directly 2 assert that .call_count is 0 Bug: 890657 Change-Id: Iffc6382ad0d9335a11c17f5ffe4d0c6ae6cbcf6c Reviewed-on: https://chromium-review.googlesource.com/1253601 Commit-Queue: Fergal Daly <fergal@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#595406}
-
Henrik Boström authored
Per-spec, tracks that are created with a receiver (e.g. addTrack or setRemoteDescription) are muted by default. Prior to this CL they were unmuted by default, whether or not they were receiving any packets. A correct implementation should unmute the tracks when RTP packets arrive. We are not quite there yet, this CL assumes that if the receiver becomes active through renegotiation it will unmute. We are careful to make sure that the track is muted on the "ontrack" event so that the application has time to wire up the "onunmute" event. By unmuting as part of processing SDP we fix the Unified Plan bug where a remote track that had previously been muted was not unmuted when becoming active again (transciever.currentDirection == 'sendrecv' or 'recvonly'), https://crbug.com/884023. This CL also makes "ontrack" fire synchronously per-spec, https://crbug.com/788558. Note that some stream events still fire asynchronously, which means they now fire after the "ontrack" event in the Unified Plan case. This is remaining work on that bug. A new file is created to test muting related behaviors, and some helper functions used this and another file are moved to RTCPeerConnection-helper.js. Bug: 884023, 777619, 788558 Change-Id: I8dc3e2adf04e72282f085779639edc73bacfc86b Reviewed-on: https://chromium-review.googlesource.com/1249066 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#595405}
-
Ivan Šandrk authored
This CL just adds the enum for the command to the command proto. DD for the feature go/remote-powerwash-command Bug: 827523 Change-Id: Iaaa3e30ca0212039120bc36b5763ad6fb789ee37 Reviewed-on: https://chromium-review.googlesource.com/1246790Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Ivan Šandrk <isandrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#595404}
-
Alexander Hendrich authored
This CL syncs the server-side changes (http://cl/214625862) and also updates the list of error codes. Bug: none Change-Id: I86ea8d9ad0cb0d29004e552194e14c8217a76b22 Reviewed-on: https://chromium-review.googlesource.com/1251083 Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#595403}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/47aa4db12689..547280e74c55 Created with: gclient setdep -r src-internal@547280e74c55 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: I9cf8de3818401fc373c211da209ac066291f9e79 Reviewed-on: https://chromium-review.googlesource.com/1253542Reviewed-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@{#595402}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/1ee9160a2e0b..156d11ddd939 git log 1ee9160a2e0b..156d11ddd939 --date=short --no-merges --format='%ad %ae %s' 2018-09-29 srte@webrtc.org Adds packet_size to rtc::SentPacket in testing code. 2018-09-29 buildbot@webrtc.org Roll chromium_revision d54862fc..11cc0baf (595183:595285) 2018-09-28 buildbot@webrtc.org Roll chromium_revision a20c193c..d54862fc (595072:595183) 2018-09-28 steveanton@webrtc.org Throw exception if MediaStreamTrack is constructed with a null native track. 2018-09-28 buildbot@webrtc.org Roll chromium_revision f63f90fb..a20c193c (594935:595072) 2018-09-28 phensman@webrtc.org Reland "Add option to call VMAF in compare_videos.py." 2018-09-28 saza@webrtc.org Revert "Remove APM-internal usage of EchoControlMobile" 2018-09-28 sakal@webrtc.org Throw IllegalStateException if native objects are used after dispose. 2018-09-28 oprypin@webrtc.org Autoroller: switch back to old-style "=" tags for TBR to work 2018-09-28 saza@webrtc.org Use low cut filtering whenever NS or AEC are enabled 2018-09-28 mbonadei@webrtc.org Enforce LGTM from owners of depends-on paths in DEPS via presubmit. 2018-09-28 srte@webrtc.org Adds simulated time scenario client. 2018-09-28 nisse@webrtc.org Change ReceiveStatistics to implement RtpPacketSinkInterface, part 1 2018-09-28 saza@webrtc.org Remove APM-internal usage of EchoControlMobile 2018-09-28 phoglund@webrtc.org Whitespace change 2 to kick bots. 2018-09-28 mbonadei@webrtc.org Remove backwards compatible macro RTC_EXPORT from sdk/. 2018-09-28 phoglund@webrtc.org Whitespace change to kick bots. 2018-09-28 nisse@webrtc.org Delete unused HTTP server code 2018-09-28 sakal@webrtc.org Revert "Add option to call VMAF in compare_videos.py." 2018-09-28 nisse@webrtc.org Reland "Replace VideoDecoder with VideoDecoderFactory in VideoReceiveStream config." 2018-09-28 kron@webrtc.org Parse two-byte header extensions. 2018-09-28 henrika@webrtc.org Improves threading model in AudioDeviceTest. 2018-09-28 crodbro@webrtc.org Move network trace calculation from analyzer to rtc_event_log_parser. 2018-09-28 mbonadei@webrtc.org Remove deprecated field_trial_default and metrics_default. 2018-09-28 peah@webrtc.org AEC3: Remove killswitches in AecState 2018-09-28 phensman@webrtc.org Add option to call VMAF in compare_videos.py. Created with: gclient setdep -r src/third_party/webrtc@156d11ddd939 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,chromium:None,chromium:None,chromium:888417,chromium:877018,chromium:877018,chromium:b/116768521 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I6c08ca97517d14263adc6de3b649334aa9a895a1 Reviewed-on: https://chromium-review.googlesource.com/1253438Reviewed-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@{#595401}
-
Sylvain Defresne authored
Official build with Firebase enabled uses variants to specify which Info.plist to use as resource for Firebase. This causes a conflict as two bundle_data have the same output path. Move the dependency on ios_firebase_resources_target to the definition of the "chrome" target, behind the check for use of the variants to prevent this conflit. Bug: none Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: If6c681f76b7315002dc1cc97c402e6f10f42efcb Reviewed-on: https://chromium-review.googlesource.com/1250924 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#595400}
-
Olga Sharonova authored
To understand why we get count mismatches for AudioOutputController stats when running the audio service in- and out-of-process. Bug: 867827 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 Change-Id: I5d1dbe62ff07d91d48ff67a49b86a14cd071623d Reviewed-on: https://chromium-review.googlesource.com/1250962Reviewed-by:
Max Morin <maxmorin@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/heads/master@{#595399}
-
Takashi Toyoshima authored
This patch makes several trivial changes: - Enforce GUARDED_BY against |clients_| and modify test only methods for that. - Initialize members in the header rather than constructor as we can as possible. - |finalized_| and |initialization_state_| do not have to be protected by |lock_|. - Enable GUARDED_BY in MidiManagerWinrt. Bug: 672793 Change-Id: I726882c502b1d5b2414c5baa33ca31c3f630072e Reviewed-on: https://chromium-review.googlesource.com/1249061Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#595398}
-
Marina Ciocea authored
Bug: 832666 Change-Id: I3ec5dbea8e34f3a9295723def845e49b2bb59af3 Reviewed-on: https://chromium-review.googlesource.com/1240280Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Marina Ciocea <marinaciocea@chromium.org> Cr-Commit-Position: refs/heads/master@{#595397}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1913722a58e2..47aa4db12689 Created with: gclient setdep -r src-internal@47aa4db12689 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: I8eeb626945a7d1b731d47a8842cbe80b6662195e Reviewed-on: https://chromium-review.googlesource.com/1253437Reviewed-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@{#595396}
-
Patrik Höglund authored
Bug: 877018 Change-Id: I5258360d3ca5175b6dcc2072c82a1f792f241836 Reviewed-on: https://chromium-review.googlesource.com/1245445Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Patrik Höglund <phoglund@chromium.org> Cr-Commit-Position: refs/heads/master@{#595395}
-
Takashi Toyoshima authored
ResourceDispatcherHostTest was modified to run with TestMode, but I forgot to setup features for each param. This patch puts right configurations and makes failed tests pass with some modification around how to manage RunLoops. Bug: 870173 Change-Id: I2b61774668ca5dd7ca2f587b68a9a8671c18fe2d Reviewed-on: https://chromium-review.googlesource.com/1249462 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#595394}
-
Marina Ciocea authored
Disable tests to unblock audio service process sandbox testing on Mac bots while reproducing the bot setup locally to debug test failures. Tests disabled: WebRtcAudioQualityBrowserTest.MANUAL_TestAutoGainControlOnLowAudio WebRtcAudioQualityBrowserTest.MANUAL_TestAutoGainIsOffWithAudioProcessingOff WebRtcAudioQualityBrowserTest.MANUAL_TestCallQualityWithAudioFromFakeDevice Bug: 882780 Change-Id: I352d3a2cb396c2f1f04bd69bec105444a591aca5 Reviewed-on: https://chromium-review.googlesource.com/1251541Reviewed-by:
Patrik Höglund <phoglund@chromium.org> Commit-Queue: Marina Ciocea <marinaciocea@chromium.org> Cr-Commit-Position: refs/heads/master@{#595393}
-
Yutaka Hirano authored
ReadableStreamBytesConsumer::reader_ has been a weak reference. This CL makes it a TraceWrapperV8Reference as it is easier to understand. Bug: 872462 Change-Id: I669daa87f854a4eab89810b7bf030fc4796d696b Reviewed-on: https://chromium-review.googlesource.com/1249281Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#595392}
-
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: I24d90f56747a5c88756c30550cab1e9c7527d936 Reviewed-on: https://chromium-review.googlesource.com/1253439Reviewed-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@{#595391}
-
Yoshifumi Inoue authored
This patch changes |NGPaintFragment::MarkLineBoxesDirtyFor()| and |NGPaintFragment::TryMarkLineBoxDirtyFor()| to mark only first line of layout object and stop scanning descendnats of culld inline box. Speed improvement for layout/attach-inlines.html is 26.50 runs/s[1] to 68.45 run/s Note: without marking dirty line, speed is 73.50 runs/s [1] http://crrev.com/c/1248622 [LayoutNG] Make line dirty marking faster Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I897224f3bd7a19036718da79bf97d0fa0076cd3d Reviewed-on: https://chromium-review.googlesource.com/1251263 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#595390}
-
Kenichi Ishibashi authored
It seems we've fixed the crash. Remove instrumentation. Bug: 887033 Change-Id: Ie0790f4b4a87455393f77c27e58bb956f669ba6b Cq-Include-Trybots: luci.chromium.try:linux_mojo Reviewed-on: https://chromium-review.googlesource.com/1253522Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#595389}
-
yusukes authored
BUG=b:116761000 TEST=None Change-Id: Id16dd20f0cf242ebed23a1521c7bbf60ba16f308 Reviewed-on: https://chromium-review.googlesource.com/1250967Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Shuhei Takahashi <nya@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595388}
-
yusukes authored
BUG=b:116761000 TEST=None Change-Id: I9573e528e85bf3d89947de5039243ac22cfb3a49 Reviewed-on: https://chromium-review.googlesource.com/1253208Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595387}
-
Etienne Bergeron authored
We want to add the "ui" category to trace fonts loading: void ShapeRunWithFont(const ShapeRunWithFontInput& in, TextRunHarfBuzz::ShapeOutput* out) { TRACE_EVENT0("ui", "RenderTextHarfBuzz::ShapeRunWithFontInternal"); R=oysteine@chromium.org Bug: 867931 Change-Id: I3d3d07516326b3320428d50d164c7fd6a5c3a90a Reviewed-on: https://chromium-review.googlesource.com/1252531Reviewed-by:oysteine <oysteine@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#595386}
-
Luis Hector Chavez authored
This change deletes a bunch of TMP that was required during the big arc::ConnectionHolder refactoring of 2017. Bug: 750563 Test: build Change-Id: Ibe6eaf55965a488855a9b306f1d79caff57646a3 Reviewed-on: https://chromium-review.googlesource.com/1253501Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Commit-Queue: Luis Hector Chavez <lhchavez@chromium.org> Cr-Commit-Position: refs/heads/master@{#595385}
-
Darren Shen authored
Gesture editing is not supported in the new UI. So we should disable the flag so that it doesn't appear in the keyboard settings page. Bug: 890134 Change-Id: I7dc3c6d05bad6e19e8cbfe0a6f89de603f4ddce5 Reviewed-on: https://chromium-review.googlesource.com/1250683Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#595384}
-
Alexandre Courbot authored
CL 1170707 has introduced an issue when we disable rendering on the VDA unittest: ImportBufferForPictureTask() would be called from AssignPictureBuffersTask() while buffers were still in the free list, resulting in EnqueueOutputRecord() trying to enqueue buffers that had still not received a picture ID. Fix this by first acquiring all buffers, before iterating on them and calling ImportBufferForPictureTask(). BUG=890656 TEST=Checked the VDA unittest passed on Hana and Cheza, with rendering both disabled and enabled. 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 Change-Id: Ied75af6d4503ff5e57b1b6bc9d2a0e1d3c2fca89 Reviewed-on: https://chromium-review.googlesource.com/1252228Reviewed-by:
Pawel Osciak <posciak@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Cr-Commit-Position: refs/heads/master@{#595383}
-
yusukes authored
It took some time for me to find the proper location. Let me update the comment while I'm at it. BUG=b:74499980 TEST=try Change-Id: I6d6f1e0948c5d36675371965b83043a230f147d8 Reviewed-on: https://chromium-review.googlesource.com/1250741Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595382}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/24c2da8c3e29..1913722a58e2 Created with: gclient setdep -r src-internal@1913722a58e2 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: I0c460d8e5fcdff2c259dcb65290654868bdabd5f Reviewed-on: https://chromium-review.googlesource.com/1253541Reviewed-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@{#595381}
-
yusukes authored
BUG=b:116761000 TEST=None Change-Id: I1a960e1d78d3c945ccf8cb3e3b775cede0fcc8f4 Reviewed-on: https://chromium-review.googlesource.com/1251223Reviewed-by:
David Jacobo <djacobo@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595380}
-
yusukes authored
BUG=b:116761000 TEST=None Change-Id: Ibb780305e22e90b589aaeef535b7220182d3bb15 Reviewed-on: https://chromium-review.googlesource.com/1251224Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Maajid <maajid@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595379}
-
yusukes authored
BUG=b:116761000 TEST=None Change-Id: Ic4c2fbc0a2fe17cb02e09539ef4c65ae1f4d50de Reviewed-on: https://chromium-review.googlesource.com/1251225Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Daichi Hirono <hirono@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595378}
-
yusukes authored
BUG=b:116761000 TEST=None Change-Id: I62b1ba37b2543789b8eedf7b1622e90711273a8a Reviewed-on: https://chromium-review.googlesource.com/1250925Reviewed-by:
Kazuhiro Inaba <kinaba@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#595377}
-
Eriko Kurimoto authored
By this change, developers don't need to update the log page UI when expanding log types to store. Bug: None Test: None Change-Id: I4fcd4d5f771a3f380376effa23ca1315f2d07a05 Reviewed-on: https://chromium-review.googlesource.com/1248525Reviewed-by:
David Tseng <dtseng@chromium.org> Reviewed-by:
Yuki Awano <yawano@chromium.org> Commit-Queue: Yuki Awano <yawano@chromium.org> Cr-Commit-Position: refs/heads/master@{#595376}
-
sangwoo.ko authored
When we try closing tabs, there might be 'unload handler' on them. In this case, we should wait for the result. So in this case, there's no closed web contents detached. Bug: 842194 Change-Id: I78b0d9f8d42631b1309f4baa8dbbfa9503564426 Reviewed-on: https://chromium-review.googlesource.com/1248883Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Sang Woo Ko <sangwoo108@chromium.org> Cr-Commit-Position: refs/heads/master@{#595375}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=cmasso@chromium.org Change-Id: Icda65c1a82586fc2588885a2e420583bb28be333 Reviewed-on: https://chromium-review.googlesource.com/1253098Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#595374}
-
momohatt authored
Spec requires that in the update of service workers, we should set the header only for the network request of the main script, and we shouldn't set headers for that of imported scripts. (https://w3c.github.io/ServiceWorker/#update-algorithm) Current ServiceWorkerNewScriptLoader sets the header for both kinds of the scripts, so this patch fixes it to conform to the spec. Change-Id: I159019e492ea212e58e6b0fcdf3f9a1e57928bdb Reviewed-on: https://chromium-review.googlesource.com/1249422 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#595373}
-
Alexandre Courbot authored
Convert the V4L2VideoDecodeAccelerator class to use the V4L2Queue. This considerably reduces its amount of code, while also making buffers lifecycle safer. BUG=792790 TEST=Made sure that VDA unittest was compiling and running on Hana Change-Id: I145778421cfc6d5951249cb9c934ac5e3b1e230b Reviewed-on: https://chromium-review.googlesource.com/1170707Reviewed-by:
Pawel Osciak <posciak@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Cr-Commit-Position: refs/heads/master@{#595372}
-
Kouhei Ueno authored
Retire the flags now that it is very unlikely we'll revert them. Bug: 711706, 773713 Change-Id: I854c5be068b42ef5fb58fe23f45ba1af107ece9a Reviewed-on: https://chromium-review.googlesource.com/1250681 Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#595371}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/92aeb7fdd6c0..24c2da8c3e29 Created with: gclient setdep -r src-internal@24c2da8c3e29 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: I7b0edcbb386675a12ef55696110cc8aaaeb06a0d Reviewed-on: https://chromium-review.googlesource.com/1253436Reviewed-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@{#595370}
-
Asami Doi authored
module scripts, and add WPT tests for ServiceWorker module scripts Implement to return registration data after evaluate module scripts and commonize WillEvaluate/DidEvaluate functions of classic and module. In addition, import module tests for ServiceWorker scripts reuse tests for DedicatedWorker. The data path in both type is "Main scirpt -> Worker script -> Main scirpt" because ServiceWorker can reply to its source only in MessageEvent. Change-Id: I2bcc1670bd43109710af30c7df3aba5ff039201a Bug: 824647 Reviewed-on: https://chromium-review.googlesource.com/1205916 Commit-Queue: Asami Doi <asamidoi@google.com> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#595369}
-
Kunihiko Sakamoto authored
Before this patch, "You are using an unsupported feature flag..." warning was shown when kSignedHTTPExchange feature flag is enabled. Now that we have fully implemented the Signed Exchange verification feature and passed security review, this patch removes that warning for kSignedHTTPExchange. Instead, we show that warning if kAllowSignedHTTPExchangeCertsWithoutExtension is enabled, because it bypasses a part of certificate check of Signed Exchange. Bug: 890137 Change-Id: I285a1e236e9a18d581468f7b1af561629ee222bd Reviewed-on: https://chromium-review.googlesource.com/1250309Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Tommy Martino <tmartino@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#595368}
-
Adam Langley authored
This change alters the code that is generated for dictionaries to use Chromium variable names. Change-Id: I5db361a1ef41dd134b2a2bf2e9af2cae14d17ad0 Reviewed-on: https://chromium-review.googlesource.com/1247232Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#595367}
-