- 20 Jul, 2020 40 commits
-
-
Maksim Moskvitin authored
The test is constantly failing on linux-chromeos builders. TBR=emaxx@chromium.org,cylai@google.com Bug: 1107426 Change-Id: I2ec9626bb2076d9382d8186578628a621b127bf6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307334Reviewed-by:
Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#789962}
-
Michael Spang authored
This is necessary to remove uses of the deprecated TaskEnvironment::DeprecatedGetMockClock function in tests. Change-Id: I56425b2bcc81b21d93c69c683b4134ee389704cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306374Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Michael Spang <spang@chromium.org> Cr-Commit-Position: refs/heads/master@{#789961}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/13480cb0ab94..6af6e625573f 2020-07-20 bclayton@google.com Update license-checker.cfg with simplified rules (#1107) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@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 Tbr: radial-bots+chrome-roll@google.com Change-Id: Ieb80823dfd03930eb879d200914a8fe6b1e4eab1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307473Reviewed-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@{#789960}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/fd5df6887258..fa504e744f9b 2020-07-20 dminor@webrtc.org Check that capture time is valid before adjusting it. 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I5cdb06394e116ab0e81f8b08bb6c177d13e94524 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307479Reviewed-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@{#789959}
-
Boris Sazonov authored
Replaces ChromeSigninController usage in AndroidSyncSettings ctor with IdentityManager. Bug: 1093998 Change-Id: I56fc23be5f2849288d2aa425ccb90a7a5a385263 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2289972 Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#789958}
-
Meera Srinivasan authored
Change-Id: Ifb0e6255745bf0e25919e53c5c463ad30de9a4bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304964 Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#789957}
-
chromium-autoroll authored
Roll ChromeOS Orderfiles from 86-4181.3-1594638142-benchmark-86.0.4204.0-r1 to 86-4181.3-1594638142-benchmark-86.0.4205.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-orderfile-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: I7488e9f082f4da2c707f809575440885fe8d2e9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307478Reviewed-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@{#789956}
-
chrome://flagsTommy Steimel authored
Bug: 1107363 Change-Id: Ie97662d5f9a81ce10ffb568a9ed573a75282d4b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307471Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Commit-Queue: Tommy Steimel <steimel@chromium.org> Cr-Commit-Position: refs/heads/master@{#789955}
-
Anand K Mistry authored
DictionaryValue::RemoveWithoutPathExpansion() is deprecated. For the case where nullptr is passed for the output argument, Value::RemoveKey() is a trivial replacement. Mostly done with the following command line, plus a bit of finesse: % git grep -l RemoveWithoutPathExpansion | \ xargs sed -E -i 's/RemoveWithoutPathExpansion\((.*), nullptr/RemoveKey\(\1/g' Bug: 646113 This CL was uploaded by git cl split. R=wjmaclean@chromium.org Change-Id: I53ed23666357b69f6f5b071ccafba3fd9f35e35a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2298763 Auto-Submit: Anand K Mistry <amistry@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Commit-Queue: James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#789954}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/343030c9..562c3f95 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I29816df57a3d78f1753e5ac182d5c2838510376d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306580Reviewed-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@{#789953}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-autoroll Please CC gbiv@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/+doc/master/autoroll/README.md Tbr: gbiv@chromium.org Change-Id: I08c4cf62e138007e8946196eeadf1bcb00b74e85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307629Reviewed-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@{#789952}
-
bttk authored
Documentation of RuntimeEnvironment#application says: Deprecated. Please migrate to androidx.test.core.app.ApplicationProvider#getApplicationContext Change-Id: I5f5b71e29edf99f4b6ee692247ea6910a0eb692c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305369Reviewed-by:
Gang Wu <gangwu@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: who/bttk <bttk@chromium.org> Cr-Commit-Position: refs/heads/master@{#789951}
-
Michael Ludwig authored
Bug: 1097104 Bug: 1098743 Change-Id: I71af4756efb3d3f030e3e61913e71a0b1c4f6148 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303670 Commit-Queue: Florin Malita <fmalita@chromium.org> Auto-Submit: Michael Ludwig <michaelludwig@google.com> Reviewed-by:
Florin Malita <fmalita@chromium.org> Cr-Commit-Position: refs/heads/master@{#789950}
-
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/perfetto-trace-processor-linux-chromium 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/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I44f63e4c8913862c70b9817dac349751ad53d8b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307368Reviewed-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@{#789949}
-
Peng Huang authored
There are many errors like: Validation Error: [ UNASSIGNED-GeneralParameterError-ExtensionNotEnabled ] Object 0: handle = 0x395107e6050, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xe92b452d | vkQueuePresentKHR() called even though the VK_KHR_incremental_present extension was not enabled. Suppose vulkan should ignore unsupported or not enabled structures in structures chain, but vulkan validation reports it. It is annoying. So fix it by not passing unsupported VkPresentRegionsKHR in VkPresentInfoKHR. Bug: None Change-Id: I7cfff50ccc3f42a08a5b0ade481e297f129f6e94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305512 Auto-Submit: Peng Huang <penghuang@chromium.org> Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#789948}
-
Alexander Dunaev authored
A recent improvement of memory usage in ozone/x11 clipboard [1] introduced a regression: copying the text stopped working because the standard MIME type for the UTF-8 encoding was not inserted into the map. This CL fixes that. [1] https://crrev.com.com/c/2292396 Change-Id: I5cedb36253a4f2be392e937f62781417eead8ad3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306252 Auto-Submit: Alexander Dunaev <adunaev@igalia.com> Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#789947}
-
Sebastien Marchand authored
This NetworkServiceClient owns a MemoryPressureListener and it's necessary to ensure that this listener gets destructed at shutdown to avoid UAFs in tests (see crbug.com/1081151). Bug: 1081151 Change-Id: Ia72a4fd35e17effe00f71018f032f2bd62118182 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2293162Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Cr-Commit-Position: refs/heads/master@{#789946}
-
Yann Dago authored
Bug: 1095206 Change-Id: I12d69fa120c1114700e947c4f56e39c0e39c13c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300401Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Yann Dago <ydago@chromium.org> Cr-Commit-Position: refs/heads/master@{#789945}
-
Mugdha Lakhani authored
Move prerender_util to components so WebLayer code can eventually use it. Bug: 1057771 Change-Id: I3b608212c12f951ae5b0a79986dd3f19e9432ea0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235619Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#789944}
-
Maksim Moskvitin authored
This reverts commit 9b0c684e. Reason for revert: likely the culprit for unit_tests failures on multiple builders (see crbug.com/1106339). Original change's description: > Reland "Reland "Turn on Media History by default"" > > This is a reland of c670ba45 > > Original change's description: > > Reland "Turn on Media History by default" > > > > This is a reland of ccf0e2f9 > > > > Fixes TSAN issue in the constructor of sql::Database > > by moving it to the main thread. > > > > Original change's description: > > > Turn on Media History by default > > > > > > BUG=1024351 > > > > > > Change-Id: Id01595e63f5f776a226087741ef602ba30b80328 > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2295224 > > > Auto-Submit: Becca Hughes <beccahughes@chromium.org> > > > Commit-Queue: Tommy Steimel <steimel@chromium.org> > > > Reviewed-by: Tommy Steimel <steimel@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#787954} > > > > Bug: 1024351 > > Change-Id: I19be665637f5c28261f7197547ddc5fe6671127e > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2296884 > > Reviewed-by: Tommy Steimel <steimel@chromium.org> > > Commit-Queue: Becca Hughes <beccahughes@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#788312} > > Bug: 1024351 > Change-Id: Ie371d56df987c19a10017050ead02922a530f2ed > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300224 > Reviewed-by: Tommy Steimel <steimel@chromium.org> > Commit-Queue: Becca Hughes <beccahughes@chromium.org> > Cr-Commit-Position: refs/heads/master@{#788721} TBR=beccahughes@chromium.org,steimel@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1024351 Change-Id: Ie255e6d2b0a88efa130e15019c2d6e5e4049b869 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306095Reviewed-by:
Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#789943}
-
Victor Hugo Vianna Silva authored
Before this CL, no SyncPrefs[1] were sent via the sync-prefs-changed WebUI event if the user was signed-in but had Sync disabled. This CL changes this, relaxing the early exit checks in PushSyncPrefs(). The change is safe because checking IsEngineInitialized() is enough to guarantee the existence of the SyncUserSettings used to fill the JS object. The CL also fixes an aspect overlooked in crrev.com/c/1718425. PushSyncPrefs() had the undocumented side-effect of setting the configuring_sync_ member, which makes no sense when the method is called in HandleSyncPrefsDispatch(). So the assignment is now moved out of PushSyncPrefs() and copied to the other callsites. [1] https://source.chromium.org/chromium/chromium/src/+/9cff09c426fb0436ce35f7c571f555e576534aaf:chrome/browser/resources/settings/people_page/sync_browser_proxy.js;l=94 Bug: 1106350 Change-Id: I9d3167d534957f10dcd878eda918bdd1510c2973 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302852Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/master@{#789942}
-
Philip Rogers authored
Change-Id: Ifd72366f13def1a12c2f16392ff378c58b23b907 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307366 Auto-Submit: Philip Rogers <pdr@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#789941}
-
Jose Dapena Paz authored
For certain cases where a div with RTL direction is set to be LTR, the algorithm for determining if bidi runs should be recalculated and reshaped was not properly ran. This is a regression introduced by https://chromium.googlesource.com/chromium/src/+/25d80f4bead925c2d9071b59a4f32146432d3e9e The solution is merging the two conditions introduced in the original patch (NeedsReshape and NeedsCollectInlines) in one that has been named NeedsReshape. Bug: 1009654, 1104827 Change-Id: I32fceb75f83b9cf2aac3ef982675a96a3ef4d3c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2297432Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/master@{#789940}
-
Tina Wang authored
This reverts commit 4977ba83. Reason for revert: Cause tree closure: https://ci.chromium.org/p/chromium/builders/ci/GPU%20Win%20x64%20Builder/16259? Original change's description: > Roll Skia from 3ba1777cebcd to 0c5bb2f776a5 (1 revision) > > https://skia.googlesource.com/skia.git/+log/3ba1777cebcd..0c5bb2f776a5 > > 2020-07-20 robertphillips@google.com Clean up some GrContext in tests > > 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 robertphillips@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: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: robertphillips@google.com > Change-Id: Iffb5c6989a63db91bae17759a4db4ce058212eb2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307365 > Reviewed-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@{#789930} TBR=robertphillips@google.com,chromium-autoroll@skia-public.iam.gserviceaccount.com Change-Id: I0bd1f105862dc551470c72d009d320e7697568ea No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: None 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 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307411Reviewed-by:
Tina Wang <tinazwang@chromium.org> Commit-Queue: Tina Wang <tinazwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#789939}
-
Bartek Nowierski authored
It should've been part of https://crrev.com/c/2306131 Bug: 1092288 Change-Id: I873c8cc804ad15e6970fb00ed0b083c490c10d8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307390 Commit-Queue: Bartek Nowierski <bartekn@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#789938}
-
Eric Seckler authored
Bug: 1105001 Change-Id: Ifbd9d8c16d7cf9f9571125207e9543d9f3705e79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304749 Auto-Submit: Eric Seckler <eseckler@chromium.org> Commit-Queue: Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#789937}
-
Francois Doray authored
This feature no longer exists and is not needed for tests. Change-Id: I5f5bb7e6ae3a4b90c0ea5638737e13eb4b20c5c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305513Reviewed-by:
Sébastien Marchand <sebmarchand@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#789936}
-
Sylvain Defresne authored
Generated by //tools/gn/roll_gn.py https://gn.googlesource.com/gn/+log/d585128c..3028c6a4 3028c6a4 [apple] Remove support for frameworks in libs 1e3fd10c [rust] Write {{sources}} ninja variable for Rust targets 46ad4c45 [xcode] Fix running XCTests and XCUITests with New Build System Change-Id: Idf49e9d103835214bd51775ed706ca8f65e952e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307213 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#789935}
-
Wez authored
Various of the tests in the suite have been individually disabled due to flakiness, but according to flake-portal most if not all of the tests in the suite are flaky, so disable them all. The individually disabled tests should be reviewed when re-enable this suite, since at least some look to be instances of the same general issue with tests flakily timing-out. TBR=pfeldman Bug: 1107396 Change-Id: Ie6540e92999503c2c83bd132f447860b4c2c8b45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307216Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Wez <wez@chromium.org> Auto-Submit: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#789934}
-
Chris Sharp authored
Bug: 1018157 Change-Id: I974bd644b14af88b753c29258f56968572501e4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2295707Reviewed-by:
Owen Min <zmin@chromium.org> Commit-Queue: Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#789933}
-
Bo Liu authored
Missing a null check that's similar to the one in DemandDrawHw. Bug: 1104821 Change-Id: I4a1199171edee81220d59f6bc42a06f88df18e95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305919 Auto-Submit: Bo <boliu@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#789932}
-
Yuki Shiino authored
There are two ExecutionContexts; one of the creation realm, and the other of the document tree. Explains the difference in a document. Change-Id: I9aa90c1d57fa4cb8528629f69e4209d1554a2109 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307389Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#789931}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/3ba1777cebcd..0c5bb2f776a5 2020-07-20 robertphillips@google.com Clean up some GrContext in tests 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 robertphillips@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: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: robertphillips@google.com Change-Id: Iffb5c6989a63db91bae17759a4db4ce058212eb2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307365Reviewed-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@{#789930}
-
Chris Sharp authored
Bug: 1018157 Change-Id: Ia2649c3aa4b105607eed3efd38e0e1b7c6615000 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2295710Reviewed-by:
Owen Min <zmin@chromium.org> Commit-Queue: Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#789929}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/c3cb2d92..343030c9 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I374386622d6a58d45583b050ece351f5a8742400 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306578Reviewed-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@{#789928}
-
Maksim Moskvitin authored
This reverts commit 982dfeb9. Reason for revert: new tests are extremely flaky. Original change's description: > [Autofill][SlimShady] General Hybrid Structure Component. > > The CL introduces a data structure to manage address components that > must support the duality of an structured and unstructured > representation. > > Change-Id: I435d82f608718c29821671dd1fa303c5fb3caa24 > Bug: 1099202 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238191 > Commit-Queue: Matthias Körber <koerber@google.com> > Reviewed-by: Dominic Battré <battre@chromium.org> > Cr-Commit-Position: refs/heads/master@{#789886} TBR=battre@chromium.org,dvadym@chromium.org,koerber@google.com,schwering@google.com Change-Id: If50e7a0ab480b96734d6325f1a7104197174aee3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1099202, 1107419 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307489Reviewed-by:
Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#789927}
-
Chris Sharp authored
Bug: 1018157 Change-Id: I3744931b8d0dd72b1b9a60db1d4890a057a245b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2295709 Commit-Queue: Chris Sharp <csharp@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#789926}
-
Peter E Conn authored
Change-Id: Iaf465c19c4478af20538722def8133c63af13239 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302759Reviewed-by:
Rayan Kanso <rayankans@chromium.org> Commit-Queue: Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#789925}
-
Andrey Zaytsev authored
When the latest version on the Omaha server matches the installed one, the server doesn't return a version string; instead, status="noupdate" is returned. Bug: 1070620 Change-Id: I114b3b67f0461f65d5db7f05009cd7dfa106a8d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307210 Auto-Submit: Andrey Zaytsev <andzaytsev@google.com> Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Cr-Commit-Position: refs/heads/master@{#789924}
-
Antonio Gomes authored
... and use WTF::Vector instead, where possible. Note that the left-over use of std::vector happens because it is used as parameter to media::MockGpuMemoryBufferVideoFramePool(). BUG=704136 R=guidou@chromium.org Change-Id: I2fcaa54a7888ad4a30fa69f16e705da4391f2837 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307409 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Auto-Submit: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#789923}
-