- 10 Jan, 2020 36 commits
-
-
Joe Mason authored
The nested "Priority Increased" event must end before the parent event so that it doesn't appear to outlive the parent. R=fdoray Change-Id: I673d7c9b364e5ac3321fabcb0a3fc6ddd5cdad88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993802 Commit-Queue: Joe Mason <joenotcharles@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#730014}
-
John Budorick authored
They don't run on any of the other android bots. Bug: 1022533 Change-Id: If398941a4f0037e1a05677f5e86e137c927b38c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994273 Commit-Queue: John Budorick <jbudorick@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Auto-Submit: John Budorick <jbudorick@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Reviewed-by:
Andrew Luo <aluo@chromium.org> Cr-Commit-Position: refs/heads/master@{#730013}
-
Vi Nguyen authored
Issue backtrace: - video_device_->CreateVideoProcessorOutputView(...) in DXVAVideoDecodeAccelerator::CopyTextureOnDecoderThread() fails because DXGI_FORMAT_R16G16B16A16_FLOAT is not supported by client's hardware. - in DXVAVideoDecodeAccelerator::Initialize, use_fp16_ = true due to "Issue 592074: Add support for different VP9 profiles". - DXGI_FORMAT_R16G16B16A16_FLOAT is in fact not supported, and CheckOutputFormatSupport(DXGI_FORMAT_R16G16B16A16_FLOAT) DXVAVideoDecodeAccelerator::CreateDX11DevManager() reflects that, and use_fp16_ = false. Proposed fix: - Make use_fp16_ an enum to reflect the fact that its non-binary states. - Because intent to use fp16 is expressed in DXVAVideoDecodeAccelerator::Initialize, which can be called before or after support for fp16 is determined, let use_fp16_ be set to kUsing for all states except kUnsupported. kUsing can be reversed later when hardware support is queried. Bug: 1032438 Change-Id: I113f26b126fdc1e0131a2362cbf19629f268f3eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974761Reviewed-by:
Frank Liberato <liberato@chromium.org> Reviewed-by:
Ted Meyer <tmathmeyer@chromium.org> Commit-Queue: Vi Nguyen <ving@microsoft.com> Cr-Commit-Position: refs/heads/master@{#730012}
-
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: I7b57298b940d89a72f56b67437d11a2b9420b1c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994404Reviewed-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@{#730011}
-
Julie Jeongeun Kim authored
This is a part of effort for using [RaisesException] when synchronously rejecting a promise. It uses [RaisesException] for //third_party/blink/renderer/core/streams/. Bug: 1001114 Change-Id: I58a9e8d6a65c6c7f33bc61ec39c121202d141cd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989321Reviewed-by:
Adam Rice <ricea@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Julie Kim <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#730010}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/8d3c0c7a1a60..1386c58de710 git log 8d3c0c7a1a60..1386c58de710 --date=short --first-parent --format='%ad %ae %s' 2020-01-09 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2020-01-09 reed@google.com remove cruft bools from canvas 2020-01-09 jvanverth@google.com Revert "Remove GrPaint::addColorTextureProcessor" 2020-01-09 robertphillips@google.com Move GrVkFormatColorTypePairIsValid assert back into GrVkGpu::check_image_info 2020-01-09 rmistry@google.com Add retries to Android compile bot for when GS returns 502s 2020-01-09 csmartdalton@google.com Speed up get_contour_count in GrTessellator.cpp 2020-01-09 herb@google.com Make SubRun accessible for GrAtlasTextOp 2020-01-09 jvanverth@google.com Hide MakeFromMTKView behind an availability flag 2020-01-09 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2020-01-09 herb@google.com Combine result calculation from both legs of if statement 2020-01-09 bsalomon@google.com Remove GrPaint::addColorTextureProcessor 2020-01-09 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2020-01-09 brianosman@google.com Fix ByteCodeGenerator's handling of specialized programs Created with: gclient setdep -r src/third_party/skia@1386c58de710 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 jvanverth@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: chromium:1037949 Tbr: jvanverth@google.com Change-Id: Iccea3b0d28bc3dae204220ed07e42fd3f20c1bc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994402Reviewed-by:
-
nancy authored
BUG=1038487 Change-Id: I05674939efdcc2678eaa0900680ccc7036526eb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993000 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#730008}
-
Reilly Grant authored
Bug: 1019783 Change-Id: I9d6e43fb52fde5f35aabae8c71663816dff15e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988812 Auto-Submit: Reilly Grant <reillyg@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#730007}
-
Julie Jeongeun Kim authored
This CL fixes the crash on media_capabilities_fuzzer. NonThrowableExceptionState was used for media_capabilities_fuzzer from crrev.com/c/1962168 but it caused DCHECK crash since NonThrowableExceptionState should not throw ThrowTypeError. It replaces NonThrowableExceptionState with IGNORE_EXCEPTION_FOR_TESTING. Bug: 1001114,1037641 Change-Id: Icb6e76e2d6d5230d264ac2838c1cb57e2cc5d8b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985620Reviewed-by:
-
Jimmy Gong authored
- This is the final CL to remove all code that is deprecated by the new printer settings UI. - Adjusts browser tests to reflect this change. Bug: 1005905 Test: Browser tests Change-Id: Ic2cf98968ca2e4ed4c19462ba8d5da75adc13376 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938043 Commit-Queue: jimmy gong <jimmyxgong@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Bailey Berro <baileyberro@chromium.org> Cr-Commit-Position: refs/heads/master@{#730005}
-
Evan Stade authored
This is the only place it's used, and it's view-specific logic so it belongs closer to the view. Bug: 1038415 Change-Id: I10bedda65753cff0b883efdff072afc683a7bc7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989884 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#730004}
-
Kalon Hinds authored
Temporarily disable the DevTools Animation Timeline test in order to land: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1920984 Bug: 963183 Change-Id: Ia1db914f4e9acccf300788084f132c5d8e53a9eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993757Reviewed-by:
Robert Paveza <Rob.Paveza@microsoft.com> Commit-Queue: Kalon Hinds <kahinds@microsoft.com> Cr-Commit-Position: refs/heads/master@{#730003}
-
Glen Robertson authored
Change-Id: I055135607864517abb3a46c8976ccf025344444c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992959 Commit-Queue: Glen Robertson <glenrob@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#730002}
-
Eric Orth authored
This is done in lieu of spreading the new interface work (which allows multiple concurrent probe runs with different contexts) from DnsTransactionFactory to DnsClient. HostResolverManager now directly interacts with DnsTransactionFactory to start/cancel probes as well as restart probes on config or connection change. Still a single probe runner instance (now owned in HostResolverManager instead of DnsClient). The next CL will complete the chain to fully allow multiple runners by inserting them into the HostResolverManager::ProbeRequestImpl objects. Slight logic change in that triggering DoH probes is now disallowed when no DoH servers are configured. This allows reusing DnsClient::CanUseSecureDnsTransactions() for checking if DoH probes are enabled. This was only ever a noop scenario before, so no practical change other than that tests that check for running probes now need to set DoH servers in the test config. Bug: 1022059 Change-Id: I9ce65739abb8fc956973c6e184dd61c52b7e4eac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985125 Commit-Queue: Eric Orth <ericorth@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Cr-Commit-Position: refs/heads/master@{#730001}
-
Mason Freed authored
The [1] CL enabled the FormControlsRefresh feature by default for Windows, Linux, and ChromeOS. In the process, many layout tests were disabled, because the form controls have a different appearance with the feature enabled. This is one of several patches rebaselining those disabled tests. [1] http://crrev.com/c/1967608 Bug: 1035582 Change-Id: I99023619889a37d62ef45b74bb3267642aab0a5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993480 Auto-Submit: Mason Freed <masonfreed@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#730000}
-
Ayu Ishii authored
This changes allows a page to have multiple input forms with autocomplete='one-time-code'. If subscribe has already been called for an SmsClient, it will silently ignore. Without this change, the page will crash upon trying to Subscribe again because each SmsClient is only allowed to be subscribed once in the SmsQueue[1]. This crash is also reproducible by reloading the page with the autocomplete input. [1] https://cs.chromium.org/chromium/src/content/browser/sms/sms_queue.cc?sq=package:chromium&g=0&l=16 Bug: 1037914 Change-Id: I130aeda2b8c9df2328393ec6b42a7cae608ef07f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981266Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Ayu Ishii <ayui@chromium.org> Cr-Commit-Position: refs/heads/master@{#729999}
-
Marijn Kruisselbrink authored
Bug: 1027737 Change-Id: Ifcce67116fc50a604b57dc7e73233eefd4729092 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993645 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#729998}
-
Avery Musbach authored
See the videos linked in https://crbug.com/1027179. Fixed: 1027179 Change-Id: Ia4f4e112b02297f3d43da81935ee1e97215c3d85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1979146Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: Avery Musbach <amusbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#729997}
-
Liquan (Max) Gu authored
Triggering condition: * Serve a payment app in HTTP * Enable --ignore-certificate-errors: this allow the payment app to be served via HTTP. Description: JourneyLogger has the Java side and the native side. The native side categorizes the payment-methods into these categories exclusively: GCard, basic-card, other. However, the Java side exclude those served via non-HTTPS scheme from being "other", and thus some payment-methods are excluded from being one of the categories. The native side has a DCHECK for the exclusivity that triggering the bug this CL is to fix. Before change: closing the payment app would cause a DCHECK failure in JourneyLogger. After change: no DCHECK failure. Code change: the Java side to include the Payment Apps served via "http" in the "other" category. Bug: 1039408 Change-Id: Ic52f27af88198874791df5d8461318c1e9ee9a96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988751Reviewed-by:
Sahel Sharify <sahel@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#729996}
-
Thomas Lukaszewicz authored
Removed unnecessary color initialization in the KeywordHintView constructor, eliminating the need to make calls to GetThemeProviderForProfile(). Performed basic cleanup and removal of unnecessary code duplication. Bug: None Change-Id: Ie8948e78cd38446f4248579626fa59a16290a8b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993485 Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#729995}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I502bfd234506aa7977d34b04e5b6ac123edc59a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993566Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#729994}
-
Peter Kasting authored
This implements suggestions from https://chromium-review.googlesource.com/c/chromium/src/+/1983539 . Bug: none Change-Id: Id621d2bfa806c48d7efaa74b34f17a959dec898e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989703 Commit-Queue: Peter Kasting <pkasting@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#729993}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/27db24581e9e..697b2241a6c7 git log 27db24581e9e..697b2241a6c7 --date=short --first-parent --format='%ad %ae %s' 2020-01-09 tobine@google.com Vulkan:Clarify volk license file name Created with: gclient setdep -r src/third_party/angle@697b2241a6c7 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 cwallez@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: cwallez@google.com Change-Id: Ib639d501e6031c3411b76fcfad4e17f86f2521d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994111Reviewed-by:
-
Kurt Horimoto authored
InfobarOverlayBrowserAgent is an OverlayBrowserAgent subclass that handles updating InfoBarDelegate state for user interaction with infobar UI presented via OverlayPresenter. For each InfobarType, an InfobarInteractionHandler will be created that updates the infobar model layer for interactions with the UI. These interaction handlers are provided to the InfobarBrowserAgent, which sets up OverlayRequestCallbackInstallers to forward responses from the UI to the interaction handlers. InfobarBannerOverlayRequestCallbackInstaller is used to forward user interaction events for infobar banner UI. The interaction handlers and the corresponding callback installers for detail sheet and modal UI will be implemented in follow-up CLs. This CL also updates AttachInfobarOverlayBrowserAgent() to install the browser agent if the feature is enabled. Subsequent CLs will be added to provide the browser agent with interaction handlers for each InfobarType. Bug: 1030357 Change-Id: I131b03e8dd1e5e4228ade4d9e01730114545fa5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989855 Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#729991}
-
Tim Song authored
There are many code sites which calculates the work area insets for positioning a tray bubble or pop-up notification. Now that the calculation is more complex, it makes sense to consolidate everything to one function. This CL also fixes insets for the message center bubble and lock screen in tablet mode. TEST=manually verified BUG=1040693 Change-Id: Ic8381a0b749e9e95b56717a239285f4bbddf7f08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993746Reviewed-by:
Ahmed Mehfooz <amehfooz@chromium.org> Commit-Queue: Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#729990}
-
Tim Song authored
For legacy reasons, there are many places that are manually drawing rounded corners in the message center, which can all be replaced by the fast rounded corner implementation in the bubble widget. Change-Id: Ife0d8f3fc74a059129cae1cd85c5bbea5ee8a2bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992016Reviewed-by:
-
Allen Bauer authored
Bug: 245409 Change-Id: I751b017bfa5187f4d33d6eeff58d8e86eba15bc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994264 Auto-Submit: Allen Bauer <kylixrd@chromium.org> Reviewed-by:
-
meacer authored
Skeleton strings are used to detect confusable hostnames. They are generated in two places: 1. During build time in make_top_domain_skeletons: This binary takes a list of hostnames and generates their skeletons to be embedded statically to the Chrome binary. 2. During runtime idn_spoof_checker.cc: This class generates skeletons of a hostname to compare against a list of known skeleton strings. Before generating a skeleton string, this class applies a few additional transformations such as diacritic removal to the hostname to be able to detect more confusable hostnames. This CL extracts the skeleton generation in IDN spoof checker code to a separate file so that make_top_domain_skeletons can apply the same transformations to input hostnames when building the static top domain list. This CL also modifies top_domain_generator binary which generates the actual trie to be embedded to the binary. The trie currently doesn't allow non-ASCII characters in its fields. This CL stores unicode hostnames in punycode to overcome this restriction. Unicode hostnames may still have non-ASCII skeleton strings, and top_domain_generator still doesn't support that. However, the current top domain list doesn't have any IDN so this isn't a blocking issue. Bug: 1040607 Change-Id: I40c654152025d910cbeb8ba32bff5b7835f00104 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992011Reviewed-by:
Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#729987}
-
Annie Sullivan authored
This also adds indexing per https://chromium.googlesource.com/chromium/src/+/master/services/metrics/ukm_api.md#controlling-the-aggregation-of-metrics Change-Id: Ib69d097d6b5c1ecd1a11c32ac709ec6c0ae59d3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989966Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Commit-Queue: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#729986}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3b19b2734385..9a83dd729bf5 git log 3b19b2734385..9a83dd729bf5 --date=short --first-parent --format='%ad %ae %s' 2020-01-09 steveanton@webrtc.org Batch process pending tasks in the libevent TaskQueue Created with: gclient setdep -r src/third_party/webrtc@9a83dd729bf5 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: Ie441a5b5874fea3dc6a550b7555770818b12e4ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994104Reviewed-by:
-
Henrique Nakashima authored
The cleanup period has already passed. Add the key to the deprecated list so it's not reused. Bug: 960767, 1022108 Change-Id: I8323c5bd897a041691f278da04861f4d799ca613 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993642Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#729984}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/12f8d69f1288..13928b7e7f1a git log 12f8d69f1288..13928b7e7f1a --date=short --first-parent --format='%ad %ae %s' 2020-01-09 ehmaldonado@chromium.org Revert "vpython: Specify interpreter to run." Created with: gclient setdep -r src/third_party/depot_tools@13928b7e7f1a If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@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 Bug: chromium:1036606 Tbr: agable@chromium.org Change-Id: Id5680e4c2400f9d73177347cee9e4e1fd57e749e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994115Reviewed-by:
-
Zhenyao Mo authored
We don't really care for devices where GPU process init takes more than 5 seconds. Even a low-end device like MS Surface Go only takes 1.2 seconds. With this CL, we can take a closer look at initialization time distribution. BUG=1039792 R=magchen@chromium.org,jwd@chromium.org Change-Id: I4363baa9743e55e27b48b48296029b305d95ddba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992692Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Reviewed-by:
Maggie Chen <magchen@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#729982}
-
Ben Pastene authored
Needed to avoid "builders should be listed in this project's commit-queue.cfg" messages in CLs like crrev.com/c/1991950. Bug: 1037892 Change-Id: I9ca588b213822c5b40482a7239603f86ac7a7ccc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993903Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#729981}
-
Tibor Goldschwendt authored
Bug: 1040256 Change-Id: Ia8e1a17d65f85d5b6ae1218835fbdb1e308c6af8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991809 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#729980}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/141fae8b9f4d..d9ef631c223a Created with: gclient setdep -r src-internal@d9ef631c223a 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: chromium:1040284 Tbr: jbudorick@google.com Change-Id: I43cb78ac1dc71133147d87eb69fc66163ef8a847 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994106Reviewed-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@{#729979}
-
- 09 Jan, 2020 4 commits
-
-
Christopher Grant authored
As per discussion with ssid@, 64-bit browser builds should not have a 32-bit unwind asset in them. R=estevenson Bug: 1038962 Change-Id: I012138cff1071d74f2722277a90758d44bf8677b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993676 Auto-Submit: Christopher Grant <cjgrant@chromium.org> Reviewed-by:
Eric Stevenson <estevenson@chromium.org> Commit-Queue: Christopher Grant <cjgrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#729978}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/f59495dd..bd2510d9 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: Ia3e28358e59d9ad271c08cd0069d9ffbc8245b88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993448Reviewed-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@{#729977}
-
Matthew Denton authored
Bug: 1038828 Change-Id: I54fd66812c69937ef6d26770341eef147e861b80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992215 Commit-Queue: Matthew Denton <mpdenton@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#729976}
-
Mila Green authored
Bug: 1031552 Change-Id: I065956f2eb6cde4354fcff23d03912836b4a14c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993142Reviewed-by:
Sorin Jianu <sorin@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Mila Green <milagreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#729975}
-
