- 25 Jul, 2020 24 commits
-
-
Wez authored
When launching the browser process for a new fuchsia.web.Context, set it to be the "critical" process for its job. This causes the kernel to automatically terminate all child processes of the Context, in the event of the browser process terminating unexpectedly. Bug: 1109148, fuchsia:56992 Change-Id: Ia4b5d51362039f301609dc9b23a4ffbe48a5d151 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316260 Commit-Queue: Wez <wez@chromium.org> Auto-Submit: Wez <wez@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#791331}
-
Alex Turner authored
Due to the extension of certain templates, the current header declaring the WTF::String overload of IdentifiabilityDigestHelper must be included before the main file, which complicates adding new users. We are also unable to add the template to the main file directly as that would be a layering violation and as we aim to reduce the usage of complicated templates. We thus change the approach to no longer define a template overload and to instead define a helper that converts the WTF::String into an IdentifiabilityToken. This helper is moved to blink/platform so that it is available outside of canvas2d. The canvas IdentifiabilityStudyHelper and its callers are modified correspondingly. They now use an IdentifiableTokenBuilder to incrementally compute its IdentifiableToken. Bug: 1102935 Change-Id: I5e7a56f629c9a5e15a07ec617932db9a4ef0b90f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212974Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
Caleb Raitto <caraitto@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Commit-Queue: Alex Turner <alexmt@chromium.org> Cr-Commit-Position: refs/heads/master@{#791330}
-
Katie Dillon authored
This QueueType is unused. Change-Id: I1282a6edd341acd8530993341e2026f19108f186 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305034Reviewed-by:
Scott Haseley <shaseley@chromium.org> Commit-Queue: Katie Dillon <kdillon@chromium.org> Cr-Commit-Position: refs/heads/master@{#791329}
-
Kyle Ju authored
Modify directory_owners_extractor.py to support the new format. See https://docs.google.com/document/d/12NIyfEpSZvVG95ypw78uA-1EiwSByVVZ-Xyl43EGpLI/preview for more information. Bug: 1102543 Change-Id: Icaa8f42f056d911f2800186826ccf695bcc988de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315216 Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#791328}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/4d9cadd58aea..0d158ac68107 2020-07-23 kainino@chromium.org Fix some bugs in buffer mapping in the wire client 2020-07-23 cwallez@chromium.org Implement sampleMask in D3D12 and OpenGL. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: Iefcd0695f25fa0109a97178ae655ffd135827522 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314842Reviewed-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@{#791327}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1595505150-b920bff7e4a91d427dfc50f17f264391e8fbe691.profdata to chrome-mac-master-1595560196-304c2c3cd13e1a2835ed6d3cda951db2ffc9e342.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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/+doc/master/autoroll/README.md Cq-Include-Trybots: chrome/try:mac-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: I3580e51a9ef8d740d553c2a37ddde8ca8b26b62c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316993Reviewed-by:
-
Utkarsh Patankar authored
This CL adds an error message to be shown when the DNR extension fails to load because the "rule_resources" in the manifest is not specified as a list of resource(s). This CL also updates PopulateItem util functions by removing the redundant checks to verify that the input is of dictionary type because that is verified by the Populate function that they call. Bug: 1105098 Change-Id: I94efca130f2c1937afd36e08f5efc4308dfbe761 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2297208 Commit-Queue: Utkarsh Patankar <utkpat@microsoft.com> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#791325}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: I3d11a3837bf3fb4a37a204aedbb36ca3386785b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318727Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#791324}
-
Livvie Lin authored
This CL also componentizes the IDN spoof checker heuristic. Change-Id: I674775cbe8dd19a2ca02551d2a72b39c782ffb82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315082 Commit-Queue: Livvie Lin <livvielin@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#791323}
-
Ali Juma authored
This CL adds arguments related to real-time lookups to the version of SafeBrowsingUrlCheckerImpl's constructor that's used on iOS. Bug: 1103220 Change-Id: I9b095860b5801e48b77e55213a1ccfd88f39e7f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314690Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Ali Juma <ajuma@chromium.org> Cr-Commit-Position: refs/heads/master@{#791322}
-
Jonathan Freed authored
This CL fixes the following issues with the action upload: 1 - removes unnecessary URL params 2 - change content type to application/x-protobuf 3 - change the request body to use the FeedActionRequest proto instead of ActionRequest Bug: b/160975622, 1108999 Change-Id: I15343ee2dcb149417932323a51055e126ffd5075 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309002Reviewed-by:
Dan H <harringtond@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Commit-Queue: Jonathan Freed <freedjm@chromium.org> Cr-Commit-Position: refs/heads/master@{#791321}
-
Alex Gough authored
On Windows 10 we can ask Windows to associate a process with a job at startup. This reduces the time during which the process handle can be used to launch more processes. Prior to Windows 10 we retain the existing call to AssignProcessToJobObject. Existing tests should cover this change. I have manually verified that processes are associated with Jobs using SysInternals ProcExp. Bug: 1050359 Change-Id: I339e42be7f30cf0e59554e89f4855dcd3af4d499 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2308916Reviewed-by:
Will Harris <wfh@chromium.org> Commit-Queue: Alex Gough <ajgo@chromium.org> Cr-Commit-Position: refs/heads/master@{#791320}
-
Jun Mukai authored
Previously, ForceUiTabletModeState uses kLockInTabletMode and kLockInClamshellMode, and use forced_ui_mode_ to enforce the tablet-mode state. However, this turns out not correct on the handling of screen_orientation_controller. To make ScreenOrientationController (and maybe some other entities) work with testing situation, ForceUiTabletModeState should set is_in_tablet_physical_state flag. In this CL: - change a simple 'force_physical_tablet_state' boolean to tri-state. - introduce new TabletModeBehaviors for the new states. - since it is considered to be 'physically tablet' status but we don't want to auto-rotate the screen due to accelerometer, create a new callback and add a mechanism to suppress the auto rotation. This CL does not change all existing ash unit tests -- that will be done in another CL. Bug: b/161253230 Test: ScreenOrientationControllerTest, tast arc.WMNonresizableConversion, make sure the screen orientation Change-Id: Ic48f8570df103fe58336faa675f9c1753bb63ee8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310773 Commit-Queue: Jun Mukai <mukai@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#791319}
-
edchin authored
Change-Id: Ia3735d1eb3f475e74f913dad24aa4e109004f420 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317086 Commit-Queue: edchin <edchin@chromium.org> Reviewed-by:
Eric Noyau <noyau@chromium.org> Cr-Commit-Position: refs/heads/master@{#791318}
-
behdad authored
This change reports the tests as a success in case of failure invalidation, and adds a field to the output.json for invalidation reason. The two failure reasons used are: - Noisy control test - Low cpu_wal_time_ratio Bug: chromium:1106934 Change-Id: Ib9217352fc8e779588a67093acaba2538b97a263 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315539Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Cr-Commit-Position: refs/heads/master@{#791317}
-
Mikel Astiz authored
This patch migrates tests away from deprecated APIs and adopts TestingProfile::Builder for tests in /chrome/browser/bookmarks. Rationale: creating or overriding keyed services after the profile has been created is problematic and known to cause hard-to-debug test flakiness, because it bypasses BrowserContextDependencyManager and often leading to use-after-free. This CL was uploaded by git cl split. R=sky@chromium.org Bug: 1106699 Change-Id: I5e31d889a94318e01c31d38d8e5c1b5222977dcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315353 Auto-Submit: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#791316}
-
Nate Chapin authored
Bug: 1107442 Change-Id: Ifc0d515e10bb73a3217dd6164aded10731e126ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316805 Commit-Queue: Nate Chapin <japhet@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#791315}
-
Mario Sanchez Prada authored
Instead of having this element owning the embedding token matching the same embedding token for the iframe/inner web contents owned by such element, let's remove it from there and simply make it so that the {Set,Get}EmbeddingToken() methods are exposed at the Frame level, available both for local and remote frames. This fixes the currently asymmetric situation where the embedding token is set on the LocalFrame representing the child frame, and then on the element (i.e. HTMLFrameOwnerElement) owning that child frame. Instead, we now will have the following situation, depending on whether we have same-site or cross-site child frames: * For same-site child frames, the embedding token is only set on the LocalFrame rendering the child frame's contents. * For cross-site child frames, the embedding token propagated via the browser process will be directly set on the RemoteFrame that receives the SetEmbeddingToken() mojo message. In both cases retrieving the embedding token of a frame owned by the HTMLFrameOwnerElement is done by simply calling GetEmbeddingToken() over the HTMLFrameOwnerElement's "content frame". Bug: 1094150 Change-Id: I72671bb19bb8a42566da0f68a8f2379212a9fcd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2299725 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Calder Kitagawa <ckitagawa@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#791314}
-
Eric Ye authored
Due to internal changes, it makes more sense to have display settings manager own whether the screen should power off, so reverting the screen off API to that state and adding a new call for setting whether it should power off. BUG=b/156411764 TEST=Build, flash to device, check behaviour Change-Id: Ib395a96ef7385640ee0bd36e0907f96c73dcd85a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316666Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Eric Ye <ericye@google.com> Cr-Commit-Position: refs/heads/master@{#791313}
-
Shengfa Lin authored
Sed behave the same on Mac and Linux for release script Bug: chromedriver:3550 Change-Id: I5d24ef995297ec0a48d8ab289ce3eed815048cc7 Notry: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315434 Commit-Queue: Shengfa Lin <shengfa@google.com> Auto-Submit: Shengfa Lin <shengfa@google.com> Reviewed-by:
-
Aleksey Kuznetsov authored
During import process from C++ part we send supported import options (checkboxes). In js part we hide not supported checkboxes. But then we send from js to C++ user choised checkboxes includes hidden (that is true by default). Need to exclude hidden checkboxes as unchecked. Bug: 1107356 Change-Id: Idf372718c632217a5474e12b4117213f12c027e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310532Reviewed-by:
dpapad <dpapad@chromium.org> Commit-Queue: dpapad <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#791311}
-
Miguel Casas authored
After consultation with PMs, we have decided to have a bit more brightness for SDR content (ToT: 50%, with this CL: 75%), hence sacrificing a bit the HDR wow effect. This only applies for the moment to kohaku (Samsung Galaxy Chromebook) and external HDR-capable, DP-connected displays. At the same time, using only 50%, or 75% of the brightness range when in SDR, kills a bit the contrast ratio, which is perceived as colors "not vivid", or greyish. This CL fixes that by adding a bit (1.25) of gamma correction in this case in DrmDisplay. With this CL, SDR colours look good (not washed out), and there's no perceived brightness change in the SDR content during SDR-HDR transitions. Bug: 958166 Change-Id: I627514e8e31129b8b8d96e528e1e51ad8bea3d92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317508Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#791310}
-
Erik Chen authored
Change-Id: Iedb3ca5f542c87634870c6c0d22c6604b4fdd734 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316787Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Auto-Submit: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#791309}
-
Garrett Beaty authored
There is likely to be a large backlog of CLs to submit that built up during the network outage. Throttling the submits that land will prevent large blamelists for CI runs. Bug: 1108842 Change-Id: I117c89082640bb30daf12b2bf5daa2e1b25c323f No-Try: true No-Tree-Checks: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317760 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Erik Staab <estaab@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: Erik Staab <estaab@chromium.org> Cr-Commit-Position: refs/heads/master@{#791308}
-
- 24 Jul, 2020 10 commits
-
-
Garrett Beaty authored
This reverts commit 735eccaa. Reason for revert: Restoring full functionality Original change's description: > Remove builders from CQ that are affected by network maintenance. > > Bug: 1108842 > Change-Id: I44ae858ebe99f33a713d814c1257359b49870a1e > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315387 > Reviewed-by: Erik Staab <estaab@chromium.org> > Reviewed-by: Ben Pastene <bpastene@chromium.org> > Commit-Queue: Garrett Beaty <gbeaty@chromium.org> > Auto-Submit: Garrett Beaty <gbeaty@chromium.org> > Cr-Commit-Position: refs/heads/master@{#791254} TBR=estaab@chromium.org,martiniss@chromium.org,bpastene@chromium.org,gbeaty@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1108842 Change-Id: I81d7c8ca20f0faa19ee7fd7270c930a44b3000df No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317861 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
-
Garrett Beaty authored
This reverts commit 291e4648. Reason for revert: Restoring full functionality Original change's description: > Remove gl_tests_passthrough and gl_tests_validating from the Linux builders > > The datacenter holding GPU's bots is offline, so these tests are > stuck. Remove them while we work on getting ATL back online. > > TBR=gbeaty > > No-Try: true > No-Tree-Checks: true > Bug: 1108842 > Change-Id: I1446673656eee48134dd271724de4a7f3279a3d3 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316689 > Reviewed-by: Haiyang Pan <hypan@google.com> > Reviewed-by: Garrett Beaty <gbeaty@chromium.org> > Commit-Queue: Haiyang Pan <hypan@google.com> > Cr-Commit-Position: refs/heads/master@{#791296} TBR=gbeaty@chromium.org,hypan@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1108842 Change-Id: I728eb56e99f06f54eb61d0b5eb5c399452858115 No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318507 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#791306}
-
Lindsay Pasricha authored
This reverts commit b5a657ac. Reason for revert: Network outage ending Original change's description: > [ios] Remove ios builders from the CQ that are affected by network maintenance. > > Bug:1108842 > Change-Id: Icad192ee46c4489972168888fc6c8bd696d5e642 > > No-Tree-Checks: true > Change-Id: Icad192ee46c4489972168888fc6c8bd696d5e642 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316325 > Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org> > Reviewed-by: Erik Staab <estaab@chromium.org> > Cr-Commit-Position: refs/heads/master@{#791301} TBR=estaab@chromium.org,lindsayw@chromium.org,gbeaty@chromium.org Change-Id: I0daeef0d31637808fe24458edbcc3c947eb553a3 No-Tree-Checks: true No-Try: true Bug: 1108842 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317808Reviewed-by:
-
Stephen Martinis authored
This reverts commit 95e22d39. Reason for revert: Potentially breaking many builders, https://crbug.com/1108314 Original change's description: > Reland "Parallelize fetching telemetry benchmark deps" > > This is a reland of 8ab0b856 > > Original change's description: > > Parallelize fetching telemetry benchmark deps > > > > The fetching script currently fetches about 2 GB (on my linux workstation) > > from cloud storage serially. This can (and is) trivially parallelizable, and > > should speed up the fetching script significantly. > > > > This script has been taking 20 minutes on mac machines for a long time. This > > will hopefully significantly speed the mac builders up. > > > > Bug: 1102597 > > Change-Id: I93d2fa2b1f4b4ef6e27e9c894a9dd4c0d0e12d7b > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285503 > > Commit-Queue: Stephen Martinis <martiniss@chromium.org> > > Reviewed-by: Wenbin Zhang <wenbinzhang@google.com> > > Reviewed-by: John Chen <johnchen@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#786521} > > Bug: 1102597 > Change-Id: I37d0055fadb26bf4eae2b0b5fe0ecc4732edde3d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2288740 > Commit-Queue: Stephen Martinis <martiniss@chromium.org> > Reviewed-by: John Chen <johnchen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#789736} TBR=martiniss@chromium.org,johnchen@chromium.org,wenbinzhang@google.com # Not skipping CQ checks because original CL landed > 1 day ago. # Tree is currently closed, trying to fix an outage No-Try: true No-Tree-Checks: true Bug: 1102597 Change-Id: If6b95395208a3136a798118e4eb229e4322c7878 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317774 Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#791304}
-
Ilia Samsonov authored
Bug: 1068400 Change-Id: I6cf1b873ba9913042c986880e7e0660210c3ba8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2295806Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Ilia Samsonov <isamsonov@google.com> Cr-Commit-Position: refs/heads/master@{#791303}
-
Garrett Beaty authored
This reverts commit 5ed2e0aa. Reason for revert: The restored capacity is experiencing connectivity issues that makes it unreliable. Original change's description: > Re-enable android-marshmallow-arm64-rel. > > The Android capacity for android-marshmallow-arm64-rel is mostly > recovered, so it is being re-enabled so that APAC and EMEA can get > Android M coverage. > > Bug: 1108842 > Change-Id: Ie865ced7efcdaa8357068db616e88801b8247840 > No-Tree-Checks: true > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316446 > Auto-Submit: Garrett Beaty <gbeaty@chromium.org> > Reviewed-by: Erik Staab <estaab@chromium.org> > Commit-Queue: Erik Staab <estaab@chromium.org> > Cr-Commit-Position: refs/heads/master@{#791298} TBR=estaab@chromium.org,bpastene@chromium.org,gbeaty@chromium.org Change-Id: I5ef6bca7e03da51ee61494e327aa9b19f1231053 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1108842 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317002Reviewed-by:
-
Lindsay Pasricha authored
Bug:1108842 Change-Id: Icad192ee46c4489972168888fc6c8bd696d5e642 No-Tree-Checks: true Change-Id: Icad192ee46c4489972168888fc6c8bd696d5e642 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316325 Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org> Reviewed-by:
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I6f1ccb7f34c0fca9ad3b193409ccae0be350f091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315495Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#791300}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=srinivassista@chromium.org Change-Id: I7a91b5ee733c9b393b8ea3e53f177444c0ad9a3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316528Reviewed-by:
-
Garrett Beaty authored
The Android capacity for android-marshmallow-arm64-rel is mostly recovered, so it is being re-enabled so that APAC and EMEA can get Android M coverage. Bug: 1108842 Change-Id: Ie865ced7efcdaa8357068db616e88801b8247840 No-Tree-Checks: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316446 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
-
- 23 Jul, 2020 6 commits
-
-
Garrett Beaty authored
Change-Id: Ib91c6c6d7876b2200d09f6e79a35d8a257375d4d No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314164 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
-
Haiyang Pan authored
The datacenter holding GPU's bots is offline, so these tests are stuck. Remove them while we work on getting ATL back online. TBR=gbeaty No-Try: true No-Tree-Checks: true Bug: 1108842 Change-Id: I1446673656eee48134dd271724de4a7f3279a3d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316689Reviewed-by:
-
Ali Juma authored
This adds an about:flags entry for real-time Safe Browsing lookups, to make it easier to enable and test. Bug: 1103213 Change-Id: I28bae0f333ece6d1f5f8f4dcf5b3c89ef6037772 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315236 Commit-Queue: Ali Juma <ajuma@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/ba0609c22877..2bda4d1319b4 2020-07-23 vapier@chromium.org cros_sdk: merge user PATH with root's PATH 2020-07-23 pprabhu@chromium.org cbuildbot: Pin the CIPD instance of the `skylab` tool 2020-07-23 tcwang@google.com afdo: Attach chrome version info to Chrome debug binary name 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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: Ic42cebef59aa4f27ddab32a76c945d5cbd9b82e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316281Reviewed-by:
-
Jonathan Ross authored
This reverts commit 26f4c62b. Reason for revert: crbug.com/1108303 regressions showing up on a large number of Graphics.Smoothness.PercentDroppedFrames graphs. We should analyze the impact and reland. Original change's description: > Re-add field trial testing config for DisableLatencyRecoveryDesktop > > Based on the data gathered from running the experiment on canary/dev and > beta, it seems that the disabling latency recovery for both main and > impl threads is an overall performance win. So, we are going to > re-enable the (now-expired) experiment on stable and move forward with > its gradual rollout. > > Bug: 993895 > Change-Id: I5c45c3cb469d14cf53193d0af6a560842ce02be2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309188 > Reviewed-by: Robert Kaplow <rkaplow@chromium.org> > Commit-Queue: Mohsen Izadi <mohsen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#790549} TBR=mohsen@chromium.org,rkaplow@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 993895 Change-Id: I0409a5a5df03b34c8e4a203482175089dac83e41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315014Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#791293}
-
Wen-Chien Wang authored
Change-Id: I4de9eaddd47175d7c295532ee292e8bf6351cfff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304975 Commit-Queue: Wen-Chien Wang <wcwang@google.com> Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#791292}
-
