- 12 Sep, 2019 40 commits
-
-
arthursonzogni authored
In preparation to fixing: https://bugs.chromium.org/p/chromium/issues/detail?id=968529 1) Remove |bypass_cache| argument everywhere. I won't have an easy way to handle this argument in the future. Luckily, this argument is always false. It can be removed. There was a long chain of caller/callee transmitting this argument for no good reason. 2) Rename ReloadPage() → ReloadFrame() ReloadPage() implementation load the document again in the observed frame. It is used for both iframes and main frames. So a renaming is required here. Bug: 968529 Change-Id: Iedf72950b7fc4aa468eab8b3b94be572d8f6b2c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796422Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Tao Bai <michaelbai@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#695968}
-
Fredrik Söderquist authored
As soon as we get a progress time that isn't "in the future" we can terminate the search. Bug: 998526 Change-Id: Ic5bea2235ba6337dc9a7759438700716a865b651 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798608 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#695967}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/9f468ceb..34915c5e Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ideec846527722f6ec892aedaf2fe7831a64565e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800142Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#695966}
-
Henrique Ferreiro authored
Convert the implementation and all users of the ash::mojom::AssistantStateObserver and AssistantStateController interfaces. Bug: 955171 Change-Id: I8af0d30eb182849b5feea16bdb199a1fe6856781 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1790444 Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#695965}
-
Nicolas Ouellet-Payeur authored
Previously, cache.dat was only updated once on startup (before loading XML sitelists from prefs), and then after all the XML sitelists were done downloading & parsing. This left a 1-minute period of time where cache.dat and Chrome's state didn't match. This would cause some back-and-forth switching between the two. Bug: 993054 Change-Id: Idb4da1c102a86392b88d7060664b16e1680c2deb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798526 Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Auto-Submit: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#695964}
-
Luciano Pacheco authored
Bug: 778674 Change-Id: Ic8b03529853bc384da64df6b13574f8796bbbda2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798254 Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Alex Danilo <adanilo@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#695963}
-
Daniel Vogelheim authored
... even if default policy application fails. Bug: 739170 Change-Id: I2a44b281eea185f5b34b3050a14dca219f38d5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1789303Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#695962}
-
Fredrik Söderquist authored
SVGSMILElement::TriggerPendingEvents() and SVGSMILElement::repeat_event_count_list_ are no longer used. Bug: 998526 Change-Id: I79f58ffc434246d022bbc255d496ac492e7daaf6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796668 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by:
-
Makoto Shimazu authored
TBR=rouslan@chromium.org No-Try: true Bug: 1003253 Change-Id: I87fbae4f1faed1f1ecc94da0b572cba235ad628b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800136Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#695960}
-
arthursonzogni authored
The BackForwardCache relies on pages to live in different BrowsingInstance. It means the current page and every pages in the BackForwardCache aren't sharing the same BrowsingInstance. The problem is that normal history navigation can specify a SiteInstance to reuse. It will be reused even when |force_browsing_instance_swap| is true in the RenderFrameHostManagerImpl. The basic idea of this CL: flush the BFCache before attempting a cross-BrowsingInstance history navigation. Bug: 993337, 999846 Change-Id: I26f1726a6ebe35eecb343b7310563e5001fc8f43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1795902Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Lowell Manners <lowell@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#695959}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/de426021b595..12b5425582ea Created with: gclient setdep -r src-internal@12b5425582ea If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: I5067c45ef93adce054c0271aefeab2b3eef13b58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800066Reviewed-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@{#695958}
-
Findit authored
This reverts commit f4d6b677. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 695951 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2Y0ZDZiNjc3N2RhMGVhY2JkY2ExNTg2Zjc1ZmM2ZWJkMGIxYzQxZDUM Sample Failed Build: https://ci.chromium.org/buildbot/chromium/linux-archive-dbg/3691 Sample Failed Step: compile Original change's description: > heap: Move test utilities into a separate lib > > This also moves IncrementalMarkingTestDriver to heap_test_utilities. > > Change-Id: I17e0dc40d71925b7ff701c37ce6a6ef502f518fa > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798671 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Anton Bikineev <bikineev@chromium.org> > Cr-Commit-Position: refs/heads/master@{#695951} Change-Id: I24f16dbde74caf22dd485b4c903cdd1b40edb9e5 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799487 Cr-Commit-Position: refs/heads/master@{#695957}
-
Roman Sorokin authored
TBR=antrim@chromium.org Bug: 1000608 Change-Id: I4cdaaf6ca1699d8d9b861b8b8789c34f256245e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1795823Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#695956}
-
Mario Sanchez Prada authored
Convert both the implementation and clients in the browser and child process for the content.mojom.ChildHistogramFetcherFactory and the content.mojo.ChildHistogramFetcher interfaces to the new Mojo types. Bug: 955171 Change-Id: I3e45219b9c027eb861507f7db9f0cac128eef5bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798357Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#695955}
-
Fredrik Söderquist authored
We no longer have a need for it - SMILAnimationSandwich::IsEmpty() will never return true in the loop in UpdateIntervals(). Tidy up the loops to use the Values() proxy. Bug: 998526 Change-Id: Ic7ebda4aece0989692293f3407c7f17c804495a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796667 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by:
-
Rakina Zata Amni authored
Currently we use strong references which will keep the shadow roots from getting garbage collected. Bug: 1002763 Change-Id: I62da84e94eaf52504efc80f1468349ee6d2f4fdc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798222Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#695953}
-
Morten Stenshorne authored
No need to have the call sites both insert a break, and flag that we broke. Change-Id: I23447c98b8aff12e13027214e416e0e7cb0df26e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796348Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#695952}
-
Anton Bikineev authored
This also moves IncrementalMarkingTestDriver to heap_test_utilities. Change-Id: I17e0dc40d71925b7ff701c37ce6a6ef502f518fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798671Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/master@{#695951}
-
Gyuyoung Kim authored
This CL converts old Mojo types to the new Mojo types in GpuService interface. - Apply pending_receiver to FooRequest arguments. Additionally, CreateVideoEncodeAcceleratorProvider of Gpu interface needs to be converted to the new Mojo type together. Bug: 955171 Change-Id: I2636edd971d6d7962614204bf81ee0c25fce8edf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1792039Reviewed-by:
Shik Chen <shik@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Victor Miura <vmiura@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#695950}
-
Morten Stenshorne authored
Some rebaselining turned out to be necessary. Change-Id: I5f7618feee3ff38dbe1d72a2f533fd161f03645f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796663Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
David Grogan <dgrogan@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#695949}
-
Makoto Shimazu authored
TBR=karandeepb@chromium.org No-Try: true Bug: 1003244 Change-Id: I935cf3775817a575d654425e648cf3337641d6a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800133Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5a2ba9996b20..578c88f047ec git log 5a2ba9996b20..578c88f047ec --date=short --no-merges --format='%ad %ae %s' 2019-09-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 0b8eca795349..f421e0e33e66 (6 commits) 2019-09-12 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go deps 2019-09-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 451d3245..4712e398 (443 commits) 2019-09-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader cebb9635a5d5..5a5ffe52a944 (4 commits) Created with: gclient setdep -r src/third_party/skia@578c88f047ec If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC mtklein@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-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 TBR=mtklein@google.com Bug: chromium:None,chromium:None,chromium:None Change-Id: Iaef50aaba3da98bd98d36bb06d46153c65180370 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800064Reviewed-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@{#695947}
-
Makoto Shimazu authored
It's failing on LSan/TSan/MSan. TBR=nhiroki@chromium.org No-Try: true Bug: 1003217 Change-Id: I9cacf67f03a631ad8fbe1db8bea8bd063d910241 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800131Reviewed-by:
-
Takashi Toyoshima authored
Now that we run tests with OOR-CORS at the fyi linux-oor-cors-rel bot, we do not need to have parameter tests for each case. Bug: 1000554 Change-Id: I3f682a788ceb7d6aa9b342c490b17e32edd51e96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1792682 Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#695945}
-
Juan Antonio Navarro Perez authored
Migrate blink perf benchmarks away from the legacy Telemetry values, using the new AddMeasurement API. Note this is just an API change, there should be no change in behavior. Bug: 999484 Change-Id: I2ae9cfd93dff8d4cdcc810f62775541703345de9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1789382Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#695944}
-
Yoichi Osato authored
This patch changes renderer to omit the encoding if all characters are ASCII. Performance: ToT: 140 MB/s Patch: 174 MB/s (+24%) Bug: 1001009 Change-Id: I2e8bf46b9e0510d0950a05ff899a3ae674d26db1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1797902 Commit-Queue: Yoichi Osato <yoichio@chromium.org> Reviewed-by:
-
Melissa Zhang authored
When an app is pinned on the shelf and that app is updated from Android app to PWA or from PWA to Android app, the shelf icon now updates to a shortcut of the new app. This behaviour is fulfilled by the new ReplacePinnedItem function in the ShelfModel. BUG=986132 Change-Id: Ib8057c63ea257fc59017e2c906949f6481ac7db6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781906Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Melissa Zhang <melzhang@chromium.org> Cr-Commit-Position: refs/heads/master@{#695942}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/6115c7945f28..de426021b595 Created with: gclient setdep -r src-internal@de426021b595 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: I61a83661959b54c7e01e4c945695f02be904171a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799279Reviewed-by:
-
Sergey Ulanov authored
Prevuiously StreamProcessorDecryptor was always decrypting data to clear buffers. This approach would not work for video where the sysmem buffers will need to be passed directly to the decoder. This change moves common audio/video functinality to FuchsiaStreamDecryptorBase and replaces StreamProcessorDecryptor with FuchsiaAudioStreamDecryptor. This will allow to add FuchsiaVideoStreamDecryptor that will integrate with the decoder to pass decoded buffers to the decoder. There are no functional changes. Bug: 997853 Change-Id: I8ee91b27318a7ebd1f1aed6355909b5daad3972b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1797061 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#695940}
-
Jeremy Roman authored
This code is more tightly entangled with the other portal code than the other event types, and should usually be reviewed by the same owners that review HTMLPortalElement and related changes. There are already a number of events that live outside core/events/, so this is not the first instance of that, either. Change-Id: I470457d065f9e669664b2b645655563f1878d059 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799399Reviewed-by:
Lucas Gadani <lfg@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#695939}
-
Ted Meyer authored
The UMA stats were wrong :( Change-Id: I400bd19b8a9be49bb3b209bc6366539eeae0bd3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799462Reviewed-by:
Frank Liberato <liberato@chromium.org> Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Cr-Commit-Position: refs/heads/master@{#695938}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/b81d59e59e07..5a2ba9996b20 git log b81d59e59e07..5a2ba9996b20 --date=short --no-merges --format='%ad %ae %s' 2019-09-12 benjaminwagner@google.com Omit path_text benches on Pixel3a Created with: gclient setdep -r src/third_party/skia@5a2ba9996b20 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC mtklein@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-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 TBR=mtklein@google.com Bug: None Change-Id: I4b178da6e2cdb525906817b5491a41241776dc39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799281Reviewed-by:
-
nancy authored
This is just the first step, moving the code from ChromeLauncherController::LaunchApp/LauncherControllerHelper::LaunchApp to AppService, and still reuse all those functions in launch_service. Also move ConvertLaunchSource to extension_apps, as next step will be remove launch_util, or see how we can better organize the launch process. So for this CL I just move code, to make it works the same as before. There will be several separate CLs to follow up for this CL: 1. Update ChromeLauncherController to use AppService launch. 2. Refactor internal apps launch process. 3. Refactor extension apps launch process. BUG=1002351 Change-Id: I87cf52c82043b45b0c2d750c62c4ffd586510098 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1795527 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Nigel Tao <nigeltao@chromium.org> Cr-Commit-Position: refs/heads/master@{#695936}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/5a5ffe52a944..d94d6a3d1103 git log 5a5ffe52a944..d94d6a3d1103 --date=short --no-merges --format='%ad %ae %s' 2019-09-12 capn@google.com Assert Reactor Float constants are finite 2019-09-12 capn@google.com Fix construction of SPIR-V constant float objects 2019-09-12 capn@google.com Fix passing sampler offset operands unchanged 2019-09-12 capn@google.com Fix storing of non-float SPIR-V constants 2019-09-12 capn@google.com Fix non-float constant creation for ASM Created with: gclient setdep -r src/third_party/swiftshader@d94d6a3d1103 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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=swiftshader-team+autoroll@google.com Bug: chromium:b/140302841,chromium:b/140302841,chromium:b/140302841,chromium:b/140302841,chromium:b/140302841 Change-Id: Iad5d7bf74b78924d1b5e8507ea091f2d138a7ad0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800002Reviewed-by:
-
Hiroshige Hayashizaki authored
As preparation for migrating wpt/upgrade-insecure-requests to the /common/security-features generator framework in https://chromium-review.googlesource.com/c/chromium/src/+/1788551, this CL introduces `downgrade` redirection type, which is to be used to test upgrading on redirects. Bug: 1001422 Change-Id: I590015cdb48c9814135dbd61a91aa318ddeba2fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1787571Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/9805913bb537..e373bb6ea58b git log 9805913bb537..e373bb6ea58b --date=short --no-merges --format='%ad %ae %s' 2019-09-12 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision fe8ed20c..0d1efbbb (695755:695897) Created with: gclient setdep -r src/third_party/webrtc@e373bb6ea58b If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:None Change-Id: Icb691e054fadcd67945b93912cdcd3fd424b9240 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799280Reviewed-by:
-
Maksim Moskvitin authored
|kSyncUSSNigori| should be checked last, since check itself has side effect (only clients, which have feature-flag checked participate in the study). Otherwise, we will have different amount of clients in control and experiment groups. Bug: 922900 Change-Id: I400b1c419c5c952d074486b644c14de8ee20227f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1798672 Auto-Submit: Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#695932}
-
Austin Tankiang authored
Remove the multi-profile browser tests as DriveFS is the default in production, so we do not need these tests. The drive migration tests required the legacy drive sync client which will be removed, so remove them too. Bug: 1002339 Change-Id: I64aa397e9981dd49fdb60a47066bb9e242f5e2f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1797843 Commit-Queue: Austin Tankiang <austinct@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#695931}
-
Kenichi Ishibashi authored
Before this CL there was a case where ReadyToRunWorkerScript() was called twice (see the linked bug for detail). The method should be called only once. To make sure ReadyToRunWorkerScript() is called only once this CL introduces another flag that tracks if InitializeGlobalScope() is already called. ResumeEvaluation() calls ReadyToRunWorkerScript() only when the flag is set. Bug: 1001967 Change-Id: I9e068208be5a11e47accc4c71da0eda2640a85dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1792477 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
-
Nigel Tao authored
BUG=1000828 Change-Id: I16870dd006c56b02ec0e58b4752f2843da192236 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1787671Reviewed-by:
-
