- 10 Oct, 2019 40 commits
-
-
Anthony Polito authored
Bug: b/140589523 Change-Id: I01e015551729dc440187735fd689486eaabd6cf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838053Reviewed-by:
Aaron Gable <agable@chromium.org> Commit-Queue: Anthony Polito <apolito@google.com> Cr-Commit-Position: refs/heads/master@{#704808}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b21973d2c0c9..847b3f98194e Created with: gclient setdep -r src-internal@847b3f98194e 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: I1316c9d93178aaf87f8dd8d1e255a3bff164b3db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854084Reviewed-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@{#704807}
-
Luke Sorenson authored
Bug: 1003037 Change-Id: I527dde7eff1e4e902d4bb81d94bdfec6867b2126 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799442Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Commit-Queue: Luke Sorenson <lasoren@chromium.org> Cr-Commit-Position: refs/heads/master@{#704806}
-
Peter Boström authored
Bug: chromium:1005563 Change-Id: I77db7e5ac5365f6aceab8b85d108ba1237b8024d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853859 Commit-Queue: Peter Boström <pbos@chromium.org> Commit-Queue: Collin Baker <collinbaker@chromium.org> Auto-Submit: Peter Boström <pbos@chromium.org> Reviewed-by:
Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#704805}
-
Daniel Hosseinian authored
In preparation of sfntly's replacement by HarfBuzz, remove sfntly_fuzzer. Any issues found by ClusterFuzz are unlikely to be fixed. Bug: 931719, 1009078 Change-Id: Ia0e3661afc5d92b57b16bf1e4fb4e4cc00b8783f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853844 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#704804}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/14bf0b9d8122..60e30b8a1a53 git log 14bf0b9d8122..60e30b8a1a53 --date=short --no-merges --format='%ad %ae %s' 2019-10-10 treehugger-gerrit@google.com Merge "tools: format Python scripts" 2019-10-10 fmayer@google.com Merge "Add canned query for bytes per type." Created with: gclient setdep -r src/third_party/perfetto@60e30b8a1a53 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@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=perfetto-bugs@google.com Bug: None Change-Id: I961a334449ced516f36870b86bea1f0aa61a5fa2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853291Reviewed-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@{#704803}
-
Morten Stenshorne authored
In the initial column balancing pass we don't know the block-size of the columns (fragmentainers). We previously set the column size to "infinity" (LayoutUnit::Max()) in this initial pass. Apart from being slightly ugly, it is also problematic, as that would cause containers of children with forced breaks to become "infinitely" tall, and we'd thus end up with "infinite" column sizes. Instead leave the fragmentainer block-size at unknown (kIndefiniteSize) in the initial column balancing pass, and have the algorithms cope with this. At the same time, replace FragmentainerSpaceAtBfcStart in NGConstraintSpace with an offset; i.e. instead of storing the remaining *space* at the nearest BFC block-start, store the *offset* from the fragmentainer block-start to the nearest BFC block-start. One good thing about this is that we only need to deal with one kIndefiniteSize field, instead of two, but this change will also come in handy when we add support for calculating the tallest unbreakable piece of content in the initial column balancing pass (in an upcoming CL). Bug: 829028 Change-Id: Id66c44452601d499d3d22c9f231576d26e10c459 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852290 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#704802}
-
jonross authored
This change is setting up a new CI bot on the chromium.gpu.fyi waterfall: "Win10 FYI x64 SkiaRenderer GL (NVIDIA)" This bot will be used for testing the SkiaRenderer configuration on Windows, backed by GL not Vulkan. This patch also includes the desired tests suites. Additionally sets up a trybot "gpu-fyi-try-win10-nvidia-skgl-64" so that we can send changes for dry-runs. Bug: 1011512 Change-Id: I56db11aa3a0147b2d496cb5bb95ebb1813e420a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841238 Commit-Queue: Jonathan Ross <jonross@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#704801}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org 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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Iec5e418841e98a31d3922dd941bdbb9d3975ea66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854044Reviewed-by:
-
Yusuke Sato authored
This allows us to abort the upgrade process when arcvm-server-proxy fails to start. BUG=b:142144019 TEST=ran the new test Change-Id: I18f5740c36d949af17a76a6e481041f08f2dad0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850365 Commit-Queue: Yusuke Sato <yusukes@chromium.org> Auto-Submit: Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Cr-Commit-Position: refs/heads/master@{#704799}
-
Mathieu Binette authored
Changes: 1) Remove `celab_version` property. We got rid of this a while back in https://crrev.com/c/1686292. 2) Increase pool sizes to 20. We are adding more and more tests and increasing the pools allows us to run more tests in parallel and complete full runs faster. 3) Exclude chrome_only tests. We have scenarios that aren't supported on Chromium (e.g. CBCM enrollment) and need to be skipped. They still run on our Chrome bots (not defined here). Blocked on https://crrev.com/c/1835668. 4) Change schedule for our CI/FYI builder to run once every 6 hours. We currently run continuously, which ends up being every ~1.5 hours. By increasing the pool sizes in 2), we'll bring that total run time to under an hour, but we really don't need more runs. 4x a day is plenty for now. We can increase it later if we need. Change-Id: Ia563b5903b9bfb4fe43e67e5127513b5c58db5f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838375 Commit-Queue: Mathieu Binette <mbinette@google.com> Reviewed-by:
-
danakj authored
We don't need to branch on both together, as sync resize is only in web tests, and emulation is not part of web tests. R=avi@chromium.org Bug: 419087 Change-Id: Ibc0db57bc45d9e5893ef3f3a9e53955679fe4207 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850411Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#704797}
-
Matt Mueller authored
The list of platforms is controlled by the BUILTIN_CERT_VERIFIER_POLICY_SUPPORTED build flag, and is set to ChromeOS and Linux in this CL. Bug: 410574 Change-Id: Ib874069df11821e30d8e7abdd3e246066a388fae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823825Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Maksim Orlovich <morlovich@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Matt Mueller <mattm@chromium.org> Cr-Commit-Position: refs/heads/master@{#704796}
-
Chris Mumford authored
The Android device serial number, specified by the --device-serial command-line option, was never passed to the chromedriver server. This resulted in chromedriver always using the first device or emulator. Bug: None Change-Id: I1a4cb1c45739f24da5ea0f6cfb3726c84ff68fa1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848264 Commit-Queue: Chris Mumford <cmumford@google.com> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#704795}
-
Henrique Nakashima authored
Change-Id: I3b946fe3713e9d0625a4ba2763f5989426bcf42e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849634 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#704794}
-
Bin Du authored
BUG=b:141495108 Change-Id: I9a440b0ecb756a48109cd25f4d10d03536ccbdbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838710 Commit-Queue: Bin Du <dubin@google.com> Reviewed-by:
Gabriel Marin <gmx@chromium.org> Cr-Commit-Position: refs/heads/master@{#704793}
-
Khushal authored
This is resulting in crashes on Adreno devices on webview. R=kbr@chromium.org Bug: 1010338 Change-Id: I27a2f3763b533390f315356678d9cea026ec0296 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850417 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Auto-Submit: Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#704792}
-
Chris Harrelson authored
In BGPT mode, they do nothing. The cc backing methods still need to stay because various non-Blink UI classes use them. Bug: 1008483 Change-Id: I7cf2f5388749dd76497f01e0a0f29dd401b01d70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838266Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#704791}
-
Martin Kreichgauer authored
Neither |fido_discovery_factory_| nor |connector_| are ever accessed past construction time. Change-Id: Idb942a50fbb8664d4482e4179b0c05dec9668422 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849438 Commit-Queue: Martin Kreichgauer <martinkr@google.com> Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#704790}
-
Yusuke Sato authored
See go/arcvm-lifetime-v2 for more context. The key differences between the original code in arcvm_launch.cc and this are: * This CL uses DCHECK and variants rather than CHECK. * This CL uses VLOG and variants rather than LOG(INFO). * This CL uses base's string/number conversion functions rather than std's. * This CL async calls to Concierge since sync ones are not usable here. * The crossystem wrapper function is reimplemented. * The unittest (which was removed in 46d42eef) is restored with some additional tests for verifying crosvm and Concierge crash handling code. BUG=b:142144019 TEST=ran the unit tests + arc.Boot Change-Id: Iba3d37aaf1527ffc76165cd93c0e121d1e226308 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848772Reviewed-by:
-
Patrick Monette authored
Bug: 932267 Change-Id: Id30a3d00dfb5034a2dbdc29b2bfed901e34e3bf7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853869 Commit-Queue: Patrick Monette <pmonette@chromium.org> Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#704788}
-
Henrique Nakashima authored
Handle null urls inside FaviconUtils.getIconDrawableWithFilter(). All callers have this behavior already, so centralize it. Change-Id: Ic3d56468dbfb42ab079903902144eb788142f676 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850781 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
-
Patrick Monette authored
Bug: 943303 Change-Id: Ifb96f74daef4b0f168da8c1509998d7184af8219 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853946 Commit-Queue: Patrick Monette <pmonette@chromium.org> Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/4b97a1108114..1ff0c181bb37 git log 4b97a1108114..1ff0c181bb37 --date=short --no-merges --format='%ad %ae %s' 2019-10-10 cepheus@frii.com Fix #1924: Emit SPV_EXT_physical_storage_buffer, not the KHR form. Created with: gclient setdep -r src/third_party/glslang/src@1ff0c181bb37 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,geofflang@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=radial-bots+chrome-roll@google.com,geofflang@google.com Bug: None Change-Id: I1bbc767068622b1a0bb4a3c5d268f9641b34ce39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853565Reviewed-by:
-
Michael Montvelishsky authored
Required for latency critical processing, for example volume Up/Down/Max control audiolization. Bug: 132990071 Test: on device Change-Id: I19b283d4de44c2586f132dfd014910f26d9608b8 Merge-With: eureka-internal/323757 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851125 Commit-Queue: Michael Montvelishsky <mont@chromium.org> Auto-Submit: Michael Montvelishsky <mont@chromium.org> Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Cr-Commit-Position: refs/heads/master@{#704784}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/f17976d01993..9e70f3614347 git log f17976d01993..9e70f3614347 --date=short --no-merges --format='%ad %ae %s' 2019-10-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 651f5a29..a1c9c889 (704530:704650) Created with: gclient setdep -r src/third_party/webrtc@9e70f3614347 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: I751fb89b19b45d75054c0021186179293d253543 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853567Reviewed-by:
-
Max Moroz authored
The length limit was selected by trying different limits on the existing corpus. 8KB appears to be the smallest limit that lets the fuzz target to be fast and efficient, without losing any edge coverage reachable with the existing corpus that we have on ClusterFuzz. The seed corpus was generated by patching |ParseDomainASCII| function in http://crrev.com/c/1850791/4/net/dns/dns_config_service_win.cc, running the DNS unittests, and then minimizing the files dumped on disk using libFuzzer's |-merge=1| option. Bug: 1004729 Change-Id: Ife871dc47e6203e4f1574db03db823661e9e0ffd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1850791Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#704782}
-
Guido Urdaneta authored
Some enterprise security systems or configurations can interfere with the audio sandbox and render audio unavailable. This policy allows enterprises to enable or disable the sandbox, which gives them flexibility to update their security setup without disrupting audio. Inspired by crrev.com/c/1465172 In addition, this CL enforces that running the APM in the audio service is possible only if the service is running in a sandboxed untility process. If the service runs in the browser, or in an unsandboxed utility process, the APM will run in the renderer process. The APM has never been configured to run unsandboxed, but it was possible to do it by explicitly setting the feature flags. Since the new policy provides another way to set flags, it is better to enforce that the APM always runs sandboxed no matter what the flag values are. Bug: 1009332 Change-Id: I09405d3058b7bf9b6f61e44583284ceaa8f0ed27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1831763 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Olga Sharonova <olka@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#704781}
-
Dominic Mazzoni authored
Bug: 1013183 Change-Id: I15fc977a86773fca393a6ebd9ab09a1d52ab2934 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853125 Commit-Queue: Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#704780}
-
Long Cheng authored
Record UMA status for time to load icon image from file. Add to record to check if we need take further action. Bug: 1010311 Change-Id: Id48d6a15faa90c7b34eaec94ebc2da5c2e27e5b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846079 Commit-Queue: Long Cheng <lgcheng@google.com> Reviewed-by:
Yury Khmel <khmel@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#704779}
-
Cammie Smith Barnes authored
It is a known limitation that http cache lookup based on a push will not be supported when split cache is enabled because the network isolation key (top frame origin, frame origin) is not available for such a request. We add an early return to the following three previously failing tests in the suite HttpCacheLookupManagerTest*: ServerPushHitCache ServerPushLookupOnUrl ServerPushPendingLookup Bug: 1009619 Change-Id: I48b3e5d89c3b6228d189da9daa4e5714ad1e1602 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853825Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Cr-Commit-Position: refs/heads/master@{#704778}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/82019e80..5697a837 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: I6e2574363a4dc5276024b318f3e421fdfbffe2ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853504Reviewed-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@{#704777}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/6e6539816196..d200a77a22cf git log 6e6539816196..d200a77a22cf --date=short --no-merges --format='%ad %ae %s' 2019-10-10 lehoangq@gmail.com Metal backend skeleton implementation. 2019-10-10 ianelliott@google.com Generate GLES 3.2 entry points Created with: gclient setdep -r src/third_party/angle@d200a77a22cf If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC geofflang@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=geofflang@google.com Bug: None Change-Id: I9a7fb02b3009b3ecea2405b6342c04790cb4f8ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852196Reviewed-by:
-
Christopher Thompson authored
This caches the results of IsTLSDeprecationConfigControlSite() in SecurityStateTabHelper, ensuring that all callers get a consistent result for |is_legacy_tls_control_site| for the duration of the page visit. Bug: 1011089 Change-Id: I7564e54c509ab927d0e3a3212859444ae4b02804 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838302 Commit-Queue: Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#704775}
-
Doug Arnett authored
Records PreviewsEligibilityReason in UKM for detected redirect loop cycle and for deny list match. Bug: 1012852 Change-Id: I8b0dc745a4ef5757d07383ed866e846839bc954d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852193Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Doug Arnett <dougarnett@chromium.org> Cr-Commit-Position: refs/heads/master@{#704774}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/df24b8a36099..51c8a7860a5a git log df24b8a36099..51c8a7860a5a --date=short --no-merges --format='%ad %ae %s' 2019-10-10 dproy@chromium.org Use chromium build for dev server tests Created with: gclient setdep -r src/third_party/catapult@51c8a7860a5a If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC simonhatch@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=simonhatch@google.com Bug: chromium:973847 Change-Id: I21e276938c000b42c021c87d19572fa84da94c83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853568Reviewed-by:
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/74dbc8af75f9..9fa72471b87d git log 74dbc8af75f9..9fa72471b87d --date=short --no-merges --format='%ad %ae %s' 2019-10-10 thestig@chromium.org Add some unit tests for fx_date_helpers.h. 2019-10-10 awscreen@chromium.org [lcms] Clusterfuzz - avoid secondary integer overflow Created with: gclient setdep -r src/third_party/pdfium@9fa72471b87d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org 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=pdfium-deps-rolls@chromium.org Bug: chromium:1009235 Change-Id: I08347b6354cfd7d4ac31e5aa568ed46727b5f2d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853288Reviewed-by:
-
Kevin McNee authored
There's nothing in these tests that is blink specific, so we make them web platform tests. Bug: None Change-Id: I88a17bcfa7e97f890d9331bdd79857e70f6c6ea9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853485Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#704771}
-
Matthew Mourgos authored
As shown in spec, this change keeps the size of control buttons between in-app and home the same. Also, the space between the shelf navigation buttons is reduced to zero when in-app. These changes improve the look of the home button's in-app <-> home animation. Bug: 1012040 Change-Id: I01c35851e20da71f88d59246088230d1ee94efe7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846181 Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Reviewed-by:
Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#704770}
-
Will Cassella authored
Previously, frame data management and scheduling responsibilities were somewhat split between the XR and XRFrameProvider classes. This CL moves all of those responsibilities into XRFrameProvider, leaving XR with the more high-level session management responsibilities. It also allows each session to have a different frame data provider instead of trying to reuse the same provider for all inline-local sessions (which is not the way the browser process sees things). Finally, it makes VROrientationDevice suspend the sensor once all inline-local sessions have been closed, and resume it once another is created. Bug: 1004008, 970854 Change-Id: Ia87ac5883ee179aa964522fc955c36add43d1370 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849098 Commit-Queue: Will Cassella <cassew@google.com> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Reviewed-by:
Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#704769}
-
