- 14 Feb, 2020 40 commits
-
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/bd710dbacd8f..08b11cafae02 git log bd710dbacd8f..08b11cafae02 --date=short --first-parent --format='%ad %ae %s' 2020-02-14 alessiob@webrtc.org iSAC config: target bitrate exposed for fixed impl 2020-02-14 danilchap@webrtc.org Rename factory names for Frequency unit type 2020-02-14 sprang@webrtc.org Revert "Refactors UlpFec and FlexFec to use a common interface." Created with: gclient setdep -r src/third_party/webrtc@08b11cafae02 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 Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ia6df7d6e6f710dbac663c7fa2fd519b2c9d8bb14 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057057Reviewed-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@{#741478}
-
Fredrik Söderquist authored
Bug: 658305 Change-Id: Ie7435fef04045b3d3c789584811eec128553db7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056728 Commit-Queue: Fredrik Söderquist <fs@opera.com> Commit-Queue: Stephen Chenney <schenney@chromium.org> Auto-Submit: Fredrik Söderquist <fs@opera.com> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#741477}
-
Ben Pastene authored
Instead of env var: https://source.chromium.org/chromium/chromium/src/+/master:third_party/chromite/cli/cros/cros_chrome_sdk.py;l=1105 The use of that env var is preventing Simple Chrome from being built with goma outside of the shell. So instead, this will pass in gomacc to the toolchain wrapper via "--gomacc-path" arg. https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/third_party/toolchain-utils/compiler_wrapper/gomacc_flag.go;l=16 Bug: 937821, 1011928 Change-Id: Ie11d78173188996ddeec36629bd0192111726459 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2052218Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#741476}
-
Kurt Catti-Schmidt authored
When TextRange positions are at MaxTextOffset, NormalizeTextRange will move them to an equivalent position at the beginning of the next node via AsTextPositionBeforeCharacter. This can cause issues with Narrator's logic that determines which character was deleted. The fix for this is to exit NormalizeTextRange if a caret or selection is visible. Note that this doesn't fully fix the issue - instead of not announcing anything, after this change it will announce one character off from the deleted character. That will require a follow-up change once we are clear what the expecations from Narrator are. This change also fixes an issue with HasVisibleCaretOrSelection. It was not properly accounting for sub-objects within text fields. This change updates it to use PlatformGetClosestPlatformObject instead of comparing against the "this" pointer. Bug: 1049682 Change-Id: Ia46fe47bde33e81f4c615609b90c71783c6b2af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2042214Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Kurt Catti-Schmidt <kschmi@microsoft.com> Cr-Commit-Position: refs/heads/master@{#741475}
-
Eric Orth authored
Bunch of minor changes/fixes in advance of moving ServerStats, server error and timeout tracking, and related logic from DnsSession to ResolveContext: *Updated method names/comments to match feedback from an earlier partial move of the DoH server selection logic. Eg we now have ServerIndexToUse() instead of NextGoodServerIndex(). *For consistency, FirstServerIndex() (previously NextFirstServerIndex()) is now used for both DoH and non-DoH and just returns 0u for DoH. *Unified server index types wherever I could find them to always be size_t. It's essentially a vector index, so the Chrome style guide says that should use size_t. *Slightly modernized the global base::BucketRanges used in ServerStats to be shared using a static method with NoDestructor rather than the static field lazy initializer stuff that was used in DnsSession. *Deleted the non-histogram logic for tracking round-trip times in ServerStats. This was dead code as only the histogram-based logic is ever used for determining timeouts. *Converted some millisecond constants/variables to TimeDelta because units are evil and result in crashed spacecraft. *Removed some DnsClient code to clear ServerStats on connection type change based on a trial name that doesn't seem to ever be enabled. Couldn't find that name string anywhere else in any Google code. *Convert LastFailure times from base::Time to base::TimeTicks. *Rename RecordRTTForHistogram() to RecordRttForUma(). "Histogram" is a very ambiguous term here because DnsSession is using histogram logic to track RTT estimation. Bug: 1022059 Change-Id: Id1af17a4b119049bc717c3a4292e230bd40b09cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050169 Commit-Queue: Eric Orth <ericorth@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#741474}
-
haozhe authored
Per the spec, Document::getAnimations() must report all Animations whose target effect is the given document. Spec: https://drafts.csswg.org/web-animations/#extensions-to-the-documentorshadowroot-interface-mixin Bug: 828585 Change-Id: I92a5cab69d0b9869fea0238e2cfb8e98d995a3b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024539 Commit-Queue: Hao Sheng <haozhes@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#741473}
-
Fredrik Söderquist authored
Bug: 1052202 Change-Id: I487afb4da3bf36feff01e3ea496b01d1d055238c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056808 Auto-Submit: Fredrik Söderquist <fs@opera.com> Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
-
Xiaocheng Hu authored
Change-Id: I1deab83b451783a6db930a1c6b98055bba57d8f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055684Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#741471}
-
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: Id6d649f7c94d69ababc9594541bef6f57759ea8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057059Reviewed-by:
-
Olivier Li authored
Similar fix to https://crrev.com/c/2056205 but adding the files to the windows list too since that bot is failing now also for my CL. Bug: 1051561 Change-Id: Ia13d9264a00ed935ff5bcbaba0760483c51aa50a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057243Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Oliver Li <olivierli@chromium.org> Cr-Commit-Position: refs/heads/master@{#741469}
-
Tom McKee authored
Bug: 943732 Change-Id: I7b8566db4dfd7e62c369f685f0d21c1644ce1cc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050607Reviewed-by:
Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#741468}
-
Vasiliy Telezhnikov authored
This CL adds three metrics to measure effectiveness of partial swap: * FrameBufferDamage part of screen that we need to redraw because it changed since last frame this buffer was used. * RootDamage part of screen that was changed this frame. * TotalDamage accounts previous two rects and other effects that change damage (e.g back drop filters). * ExtraDamage accounts all additional damage to the frame including buffer queue frame damage. Change-Id: I507d60dd74602ee25893351d5e3d2b0bd8a8e4c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2054274Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#741467}
-
Manu Cornet authored
Target bounds are now tracked by their relevant shelf components. The target opacity is the sole remaining field in this struct, and can be kept as a simple float field instead. Change-Id: I2599fd0994e860d959046b87e860927cbe3b8df2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057106Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#741466}
-
Kent Tamura authored
* Add |final| to SelectType subclasses so that compilers can omit vtbl lookup code * Add |const| to SelectType::select_ to avoid getting its value from memory multiple times in a single SelectType method This CL has no behavior changes. Bug: 1052232 Change-Id: I6c941defd9c8a4f428abd2a62e673f026daddb2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057223 Auto-Submit: Kent Tamura <tkent@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#741465}
-
Etienne Bergeron authored
This CL is adding trace events for the known issues that can caused a waitable event or Disk IO on the IO-Thread. The goal of this change is to allow to track jank and identify the related bugs by using the slow-reports. Currently, the ScopedBlockingCall shows a trace event for the raw primitive but it is time consuming to get back to the source of the bug. By adding a trace event on the ScopedAllow*, it is easy to figure out the cause of the blocking call. Bug: 1047794 Change-Id: I05734d7344f9eca0307be3af08431fdc5dccf439 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031440 Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#741464}
-
Carlos IL authored
PageInfo in Android currently shows the full url used to navigate, including username@ if the navigation included it. This CL changes it so it omits it. This does not affect the copy function which will still copy the URL including the username@ part. This matches the omnibox functionality on desktop. Bug: 1050011 Change-Id: I3b6794f94774a7300f5afe43262b130c0d534949 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055806Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Carlos IL <carlosil@chromium.org> Cr-Commit-Position: refs/heads/master@{#741463}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/379d0c30470e..dfbb2ba942c1 Created with: gclient setdep -r src-internal@dfbb2ba942c1 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 Bug: None Tbr: jbudorick@google.com Change-Id: I718e1107093cbb5dfd46da8437bb4410bdbe55c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057050Reviewed-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@{#741462}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/6df58e2de32f..cade6994aebe git log 6df58e2de32f..cade6994aebe --date=short --first-parent --format='%ad %ae %s' 2020-02-14 vapier@chromium.org signing: convert to python3 only 2020-02-14 vapier@chromium.org build_api: switch to python3 only 2020-02-14 vapier@chromium.org run_tests: detect stale bin/ symlinks 2020-02-14 vapier@chromium.org licensing: convert to python3 only 2020-02-13 seanabraham@chromium.org cros_branch: remove upstream branch name for new branch name 2020-02-13 rrangel@chromium.org fwgdb: Use ServodClientParser 2020-02-13 lamontjones@chromium.org api: compile api 2020-02-13 mathewk@chromium.org vm: Ensure that kvm is available before enabling it 2020-02-13 vapier@chromium.org replication_util: switch to python3 only Created with: gclient setdep -r src/third_party/chromite@cade6994aebe If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-kevin-rel Bug: None Tbr: chrome-os-gardeners@google.com Change-Id: Ib67372ebb692c17396306d1eb51cd929ed5a0c62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057053Reviewed-by:
-
kylechar authored
This is a reland of 9a8afe6e. Leave the test as disabled on Fuchsia since it's not reliable there. Original change's description: > Enable SkiaCopyOutputScalingPixelTest > > The test should work with SkiaRenderer now. > > Bug: 1047217 > Change-Id: Ib467e836cf7abc3a8d00b606d81ed33470929db2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050616 > Reviewed-by: Jonathan Backer <backer@chromium.org> > Commit-Queue: kylechar <kylechar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#740428} Bug: 1047217 Change-Id: Ia3bc94c4c8abe4c2cb125b9b448de8fec23d09ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057104Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#741460}
-
John Delaney authored
The match command documentation currently asks for "document-origin" but actually uses "document_origin", which is hard to recognize. This CL fixes the documentation and also adds a more verbose error for when the required arguments are not supplied. Change-Id: Idd5f82a61f0628677f8f69633d3e783538a0c253 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055690Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Commit-Queue: John Delaney <johnidel@chromium.org> Cr-Commit-Position: refs/heads/master@{#741459}
-
Wez authored
Change-Id: I7d356012e6acb40b6305a43ed537796c313c1dd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050476 Auto-Submit: Wez <wez@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#741458}
-
John Chen authored
This reverts commit 1cd142b4. Reason for revert: Causing build failures on Android x86 Builder (dbg) Original change's description: > Allow build ChromeDriver during Android build > > While build for android, ChromeDriver can be built using host toolchain. > > Bug: 1050709 > Change-Id: Ifc7b97f4474e73e3025ec33450bdfd29559ba087 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050872 > Reviewed-by: John Budorick <jbudorick@chromium.org> > Commit-Queue: John Chen <johnchen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#741146} TBR=johnchen@chromium.org,jbudorick@chromium.org Change-Id: I343851d232030913b08730c478f07dbeb6657792 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1050709, 1052318 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057109Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#741457}
-
Darin Fisher authored
This eliminates Blink public WebPrerender and WebPrerenderingSupport interfaces in favor of having core/loader talk directly via mojo to the browser-side PrerenderProcessor. This deletes a bunch of code :) Move corresponding interfaces to blink/public/mojom/prerender/. PrerenderCanceler remains defined in chrome/common/ as it is used by the renderer process that is created to load a prerendered / prefetched web page. Onion soup of this part could be a future CL. Change-Id: If7ec0f417930f1a72a515a7fb7ae288a2ba843cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2042139 Commit-Queue: Darin Fisher <darin@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#741456}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/eaff904e7260..3a3e7d4dd2bc git log eaff904e7260..3a3e7d4dd2bc --date=short --first-parent --format='%ad %ae %s' 2020-02-14 aleino@nvidia.com Don't skip functional.layout_binding.ubo.vertex_binding_max on NV/D3D11 Created with: gclient setdep -r src/third_party/angle@3a3e7d4dd2bc 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 courtneygo@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-asan;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: courtneygo@google.com Change-Id: Ieefd9831592c37d949e3896b8447fd013479d608 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057049Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/02808dc0a181..46b98e70c127 git log 02808dc0a181..46b98e70c127 --date=short --first-parent --format='%ad %ae %s' 2020-02-14 lalitm@google.com Merge "tp: only create tid/pid 0 <-> utid/upid 0 mappings for traces with ftrace" 2020-02-14 taylori@google.com Merge "perfetto-ui: Add args" 2020-02-13 primiano@google.com TraceProcessor: fix trace_bounds computation 2020-02-13 primiano@google.com Minor cleanup to string conversions. Expose TraceProcessor EOF 2020-02-13 treehugger-gerrit@google.com Merge "perf sampling: minimal UI for stacks as slice columns" 2020-02-13 hjd@google.com Merge "Fix Mac compile of api_integrationtest.cc" 2020-02-13 fmayer@google.com Merge "Remove stale comment." 2020-02-13 lalitm@google.com Merge "tp: make diff testing script run all tests by default" 2020-02-13 lalitm@google.com Merge "tp: cleanup diff test script in preperation for unified execution" 2020-02-13 ddrone@google.com Add frame_tree_node_id to LatencyInfo.Flow event 2020-02-12 treehugger-gerrit@google.com Merge "processor: Override/extend args correctly when merging" 2020-02-12 treehugger-gerrit@google.com Merge "TrackEvent: Register available categories with service" 2020-02-12 treehugger-gerrit@google.com Merge "UI: update logo and sidebar animation" Created with: gclient setdep -r src/third_party/perfetto@46b98e70c127 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 Bug: chromium:148777631,chromium:149483774 Tbr: perfetto-bugs@google.com Change-Id: I4c50e46625876e6bbe9f14063e785660fc539836 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057048Reviewed-by:
-
Mugdha Lakhani authored
This change moves three accessibility strings from chrome:// to components:// so they can be set for the security status icon in the WebLayer URL bar. Bug: 1025607 Change-Id: I7298a14efbaa663315438c2a1675e0e248cc5ad4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047025Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#741453}
-
Tina Wang authored
Some dependencies haven't been removed when removed unused imports. Change-Id: Ic31d2bfae3249e285ca6d2aa1405681a031af5b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055023 Commit-Queue: Tina Wang <tinazwang@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#741452}
-
Dong Hwi Lee authored
Add a test with a realistic sitemap.xml. Change-Id: I5ca40acab728553593da41491a52c11902bcb5d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051875Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Dong-Hwi Lee <leedh@google.com> Cr-Commit-Position: refs/heads/master@{#741451}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/ddad4c60aec3..f46f19b98c0d git log ddad4c60aec3..f46f19b98c0d --date=short --first-parent --format='%ad %ae %s' 2020-02-14 bsalomon@google.com Add support for implementing ShaderMode::kRepeat with MIPs in GrTextureEffect. Created with: gclient setdep -r src/third_party/skia@f46f19b98c0d 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 stani@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 Bug: None Tbr: stani@google.com Change-Id: Ib69b460dabeae487293f3ecb6178f8eac749f8ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056487Reviewed-by:
-
Emre Kanlikilicer authored
Bug: 1051082: Remove startup sentinel during gcpw uninstall. Change-Id: I4d2db7eda7778abf791a1bada4a533562a284195 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050621Reviewed-by:
Tien Mai <tienmai@chromium.org> Reviewed-by:
Yusuf Sengul <yusufsn@google.com> Commit-Queue: Emre Kanlikilicer <emreknlk@google.com> Cr-Commit-Position: refs/heads/master@{#741449}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/e245d1a20821..65862c545fec git log e245d1a20821..65862c545fec --date=short --first-parent --format='%ad %ae %s' 2020-02-14 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-02-14 aerotwist@chromium.org Updates node_modules to remove resemblejs 2020-02-14 aerotwist@chromium.org Move screenshot helper Created with: gclient setdep -r src/third_party/devtools-frontend/src@65862c545fec If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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 Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I93059a99e3b86f75347549c447b05ecdceef98c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056486Reviewed-by:
-
jonross authored
Originally we were having each callsite to PeakGpuMemoryTracker provide a callback to perform UMA reporting. However we had wished to bring the UMA work directly into the class. Upcoming plans with allocation source metrics would lead to too much boilerplate code being duplicated in all the callsites. This change refactors the UMA handling to be within PeakGpuMemoryTracker itself. With the callsites telling it which type of user interaction is being observed. Bug: 1001168 Change-Id: I4229025941c8d265af958015713502c63b19800b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026117Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#741447}
-
Oleg Davydov authored
Current implementation of FakeCWS doesn't support signed hashes for extensions' resources. Therefore content verification of extensions provided by FakeCWS may fail and extensions will be false-positively marked as corrupted. This commit disables content verification when FakeCWS is used, as we don't need it in corresponding tests. Also this commit removes condition when overriding WebStore URLs for ExtensionsClient, now they are always updated. That condition only added possible flakiness. In tests ExtensionsClient was initialized after command line changes, so it used overridden values anyway. Bug: 1051513 Change-Id: Ie74553f6f778efa0e82f17f64149d688e320f151 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051931 Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#741446}
-
Stephen McGruer authored
As per https://crbug.com/1051944#c2 Bug: 1051944 Change-Id: I93e399580f1b4e4da6e7f3317602a9f2b591244a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057047Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#741445}
-
Mugdha Lakhani authored
There was a naming conflict with url_bar.xml from chrome:// which caused some chrome smoke tests to fail. This CL fixes that and tries to reland the original change. Descrption from the original commit: UrlBarView is now a LinearLayout with its own resource XML. It contains a security icon (currently always the lock icon) and a TextView containing current display URL. Here's a recording of the UI after this change: https://drive.google.com/a/google.com/file/d/1q8IzYALoPYd8KLcln4cMEnRjIT6ox_so/view?usp=sharing TBR=dtrainor@chromium.org,tommycli@chromium.org Bug: 1025607 Change-Id: I47f94905de9a220f02a589814a7eada550e1b303 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049980 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
-
Alexandre Courbot authored
When using imported input buffers, it is very possible that the system will give us buffers of a coded size larger than the one we specified when negotiating the input format with the encoder. In this case, we have to call S_FMT again in order to set the actual input buffer format. However doing so also has the effect of resetting the crop rectangle to the new resolution. Make sure to set the crop right after, otherwise we may end up with an invalid resolution in the encoded stream. BUG=b:149451052 BUG=b:147851828 TEST=android.media.cts.EncodeDecodeTest passing. Change-Id: I64a5f56a71b469b32d809419ff901516d1032328 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056403Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Cr-Commit-Position: refs/heads/master@{#741443}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/142ac8d3..d249a8cf 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: I858fa9c9b1fa268c8a45f1c527cbc27447678db2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056644Reviewed-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@{#741442}
-
Ian Clelland authored
Change-Id: Ida8184de82d7ed7c695a89ec7142f08485f002a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055669 Auto-Submit: Ian Clelland <iclelland@chromium.org> Reviewed-by:
-
Sky Malice authored
Bug: 1050094 Change-Id: I3abcd08318fd6a0f8e6fccc95664da59f37f168c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051737 Commit-Queue: Sky Malice <skym@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Reviewed-by:
Cathy Li <chili@chromium.org> Cr-Commit-Position: refs/heads/master@{#741440}
-
Finnur Thorarinsson authored
A recent refactoring of SelectableItemView[Base] introduced a regression where a white selection circle would show on top of all images in the Photo Picker. The fix is to switch inheritance from SelectableItemView to SelectableItemViewBase, which doesn't inflate any extra xml. Bug: 1051523, 656015 Change-Id: Ie938b31ba79152d1573363cc567c937aa9d430e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056806 Commit-Queue: Theresa <twellington@chromium.org> Auto-Submit: Finnur Thorarinsson <finnur@chromium.org> Reviewed-by:
-
