- 25 Aug, 2020 40 commits
-
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I0954856d061075ec3914447e189f983bc1e09ee4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375891Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#801500}
-
Shakti Sahu authored
This is a reland of 2a107111 Fixed a include header in the original CL that was causing build failure. Original change's description: > Video Tutorials : Modularized JNI bridge > > This CL moves the VideoTutorialServiceFactory and the JNI bridge into > the internal target. A corresponding public factory class is generated > from the internal factory using android_library_factory function. The > JNI function lives in video_tutorial_service_bridge_factory.cc which is > included in chrome/browser target while still living in > chrome/browser/video_tutorials/internal. > > Bug: 1120097 > Change-Id: I4cbc7e2763012e3780a28f58bf14e3374464e20e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368474 > Reviewed-by: Henrique Nakashima <hnakashima@chromium.org> > Reviewed-by: David Trainor <dtrainor@chromium.org> > Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#801312} TBR=dtrainor@chromium.org,hnakashima@chromium.org Bug: 1120097 Change-Id: Ieefc1d53ccb61798a43dd28b482da5eb59621e96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375786Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Shakti Sahu <shaktisahu@chromium.org> Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> Cr-Commit-Position: refs/heads/master@{#801499}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/70f0b007..288014f2 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: I639912c2319c1d8e09c14cb606addf206986145f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376005Reviewed-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@{#801498}
-
Etienne Pierre-doray authored
Current implementation delegates to Join(), but there's no need to bump priority of a canceled task. This CL simply calls WillJoin(). There's a subtle race that was hidden by priority bump (which takes ThreadGroup::lock_). 1- Thread B calls GetRemainingConcurrency(). state_ is not canceled. 2- Thread A calls JobHandle::Cancel() and frees job state. 3- Thread B calls GetMaxConcurrency() -> use after free RemoveJobTaskSource() becomes necessary again to make sure the task_source doesn't become dangling while still in the queue. Once JobHandle::Cancel() returns, it's ok if we end up with dangling references of job_task_source since it's already canceled. Change-Id: I6cf831b64fc75e555e32ae9b399342d64ed3f7d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369259 Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#801497}
-
Andre Le authored
- Change button and title to match quick settings style. - Settings button always stay in top right. - Remove white separator when scrolling in IME Menu. Screenshot: https://screenshot.googleplex.com/PTwj2MASeNH BUG=1114949 Change-Id: I3619643bb49bf08542fdaaf75f52582173b01199 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368773 Commit-Queue: Andre Le <leandre@chromium.org> Reviewed-by:
Tim Song <tengs@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#801496}
-
Kyle Milka authored
Bug: 1009124 Change-Id: I0d15bfdff9fe26177297ba3fe799567ec595d2ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2327646Reviewed-by:
Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Kyle Milka <kmilka@chromium.org> Cr-Commit-Position: refs/heads/master@{#801495}
-
Pin-chih Lin authored
In test scheme while snd-aloop is probed, "Loopback Playback" and "Loopback Capture" will be shown in system tray as ALSA loopback output and input device. The input gain could be also scrollable after "Modify mic gainin the system tray" is enabled in chrome://flags. BUG=1083465 TEST=Checked "Loopback Playback" and "Loopback Capture" are in system tray when snd-aloop is probed. TEST=Checked the scrolls of playback volume and capture gain are both valid. Change-Id: Iacfc73e76d4ecbb1380b1488b5b7acee4c3c788b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352129Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Hsinyu Chao <hychao@chromium.org> Reviewed-by:
Bailey Berro <baileyberro@chromium.org> Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Auto-Submit: Pin-chih Lin <johnylin@chromium.org> Cr-Commit-Position: refs/heads/master@{#801494}
-
Greg Kerr authored
This CL removes a number of expired histograms related to keychain reauthorization. Bug: 1088511 Change-Id: I7faa87c0327efaf4eee2d4ad8d1d89cba821d9d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373263 Commit-Queue: Greg Kerr <kerrnel@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Greg Kerr <kerrnel@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Cr-Commit-Position: refs/heads/master@{#801493}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/41db2fb64914..ff77947e7ecc 2020-08-25 aninditaghosh@google.com tp: Bind httpd to IPv6 address. 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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: chromium:163312367,chromium:163312727,chromium:164038530 Tbr: perfetto-bugs@google.com Change-Id: Idc8161357d2dfa582f8646334cf9c1af99acee66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375710Reviewed-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@{#801492}
-
Sky Malice authored
Previously FirstRunAppRestrictionInfo had a static instance that callers used. Because it could be long lived, it meant that it also listened for changes to the device. This API for changes exposed our problems, because it would crash when trying to stop listening for changes if it never started listening. The reason for the incorrect listening is that the FirstRunActivity was destroying/stopping listening. But it was possible for two separate ChromeIntentDispatcher/FirstRunActivity pairs to be calling into it. And so the first FirstRunActivity would shutdown before the second was done starting up. This had the potential to cause subsequent problems if we just guarded against the crash. So instead of having a long lived static instance, we now have a temporary that ChromeIntentDispatcher starts, and then FirstRunActivity takes strong ownership over. This fixes the fundamental problem of the two FirstRunActivities destroying the FirstRunAppRestrictionInfo that the other activity is using. However, it comes to a slight performance hit when there are two FirstRunActivities present. Because this is an edge case, having safe code seems more important than performance. Since FirstRunAppRestrictionInfo is currently not long lived, it doesn't really warrant actually listening for changes on the device. Removed the listening code for simplicity. Bug: 1119548 Change-Id: I2dea7b20222c2d433e5db0410bb96607298db5e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2371642Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Wenyu Fu <wenyufu@chromium.org> Commit-Queue: Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#801491}
-
chromium-autoroll authored
Roll ChromeOS Airmont AFDO profile from 86-4183.74-1598264968-benchmark-86.0.4240.3-r1 to 86-4183.74-1598264968-benchmark-86.0.4240.6-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-afdo-airmont-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: I3e542fedc7b837d636f2d5921b010c9ac1f312e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375712Reviewed-by:
-
Jazz Xu authored
This CL adds MediaNotificationProvider and MediaNotificationProviderObserver interface serve as a connection between ash and browser. Which will be used to send MediaNotificationListViews and media session info from browser to ash. Bug: 1111420 Change-Id: I276ff5d10642450ab392096c0a6db7c00a1c1c41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315092Reviewed-by:
Tommy Steimel <steimel@chromium.org> Reviewed-by:
-
Dylan Cutler authored
Bug: 973801 Change-Id: I1d19acc974abf0fdad068296339d719c51b6b129 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368466 Commit-Queue: Dylan Cutler <dylancutler@google.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Cr-Commit-Position: refs/heads/master@{#801488}
-
Leonid Baraz authored
The bug assigned incorrect first seq number when StorageQueue consisted of multifile files. Also, fixed incorrect setting of StorageQueue options in the test, and added a new test that democased the failure. Bug: b:165851833 Change-Id: I6bfcb96eada2b8a47e2a10ca711ba414e8de61d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373426Reviewed-by:
Zach Trudo <zatrudo@google.com> Commit-Queue: Zach Trudo <zatrudo@google.com> Auto-Submit: Leonid Baraz <lbaraz@chromium.org> Cr-Commit-Position: refs/heads/master@{#801487}
-
Christian Biesinger authored
The -17 test started failing because this does not support the automatic minimum size yet. R=ikilpatrick@chromium.org Bug: 1083010 Change-Id: I8dbbf26021529faef9a16f85322914dcab9cafcb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369420 Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#801486}
-
chromium-autoroll authored
Roll ChromeOS Silvermont AFDO profile from 86-4183.74-1598267562-benchmark-86.0.4240.3-r1 to 86-4183.74-1598267562-benchmark-86.0.4240.6-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-afdo-silvermont-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: Ide2b8f85be51ee2fc3796d255085cc88148e943c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375714Reviewed-by:
-
Mohamed Amir Yosef authored
Change-Id: Ifc007754b08fad94f9e433311d7f84bae571e6b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2374450Reviewed-by:
John Wu <jzw@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#801484}
-
Stephen Nusko authored
ASYNC events are deprecated and unsupported in the new perfetto UI. This migration ensures they continue to show up properly and are supported in the new UI. Change-Id: If74d889209021f68f23615dc36b1962951ef0ca2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375333Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Etienne Bergeron <etienneb@chromium.org> Commit-Queue: Stephen Nusko <nuskos@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Auto-Submit: Stephen Nusko <nuskos@chromium.org> Cr-Commit-Position: refs/heads/master@{#801483}
-
Charlie Hu authored
Change-Id: Ic4e644e9cb27572eb67d49ab182e4897ea8fee77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363294 Commit-Queue: Charlie Hu <chenleihu@google.com> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#801482}
-
Xiaocheng Hu authored
[Sheriff] Disable LayerTreeHostTestAbortedCommitDoesntStallSynchronousCompositor.RunMultiThread_DelegatingRenderer Bug: 1121690 Change-Id: I7abee836e9c64300938cb991e0b73caf3f9f5461 NoTry: True Tbr: wangxianzhu@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375893Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#801481}
-
Aleks Totic authored
Read correct CSS axis when cells are orthogonal. Also, couple of cleanup one-liners to lighten the big patch. Bug: 958381 Change-Id: Ifece05e61f4ed42c6e1965bda1a58034f224d6f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373272 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
-
Nick Burris authored
In crrev.com/c/2254058, AndroidPaymentAppFinder was changed to mark app store payment apps as preferred payment apps. The patch made the assumption that the payment app was valid, which is not necessarily the case, e.g. if the TWA has an invalid app store payment app identifier. This patch checks for the app rather than asserting. Verified fix with the test TWA from the bug. Bug: 1120346 Change-Id: Ibd3f5bcd8f562d46583b1e580a3fc997d848c58f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369255Reviewed-by:
Liquan (Max) Gu <maxlg@chromium.org> Commit-Queue: Nick Burris <nburris@chromium.org> Cr-Commit-Position: refs/heads/master@{#801479}
-
Anders Hartvoll Ruud authored
Currently we are creating a new ScrollTimeline for every frame, even for is_animation_style_change==true, in which case we don't even look at the 'timeline' variable. This CL moves the timeline computation to the branch handling new animations, such that we don't waste time by creating timelines that are never used. Bug: 1074052 Change-Id: If9327fa9dbc97666aae3377cc8b22deb95382932 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2374448 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#801478}
-
Alex Ilin authored
Standard context menu options aren't available in profile picker web contents. For example, "View page source" and "Inspect" don't work at all in the system profile. This change also helps fix the bug when the profile picker window closes after dismissing the context menu (I don't know what's the cause of this though). Bug: 1121543, 1121541 Change-Id: Iad91145481c8b5d8184f0bf600cea5a8a39f158c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2374451Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#801477}
-
Koji Ishii authored
|emphasis_mark_height| could be zero if `font-size` is zero, but the DCHECK did not include the case. Bug: 1105882 Change-Id: Ia5665778ecb2d396d156c6b6e2e8a2f69151889e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2374918 Auto-Submit: Koji Ishii <kojii@chromium.org> Reviewed-by:
-
Garrett Beaty authored
Macs all have SSDs, so generating ssd:0 for builderless mac builders forces the definition to also specify ssd=None. Change-Id: I61b09dab79e9ec37867c6d24c39982f360083a5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368322Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#801475}
-
Alex Chau authored
- Moved check for active profile into InvalidateSurfaceState, so send/receive surface can still be registered without profile being active - OnNearbyProcessStopped will InvalidateSurfaceState to potentially restart the flow if profile is still active Bug: 1120087 Change-Id: I40cc43949a46808d2c090c1681d34e0450f62fd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375289 Commit-Queue: Alex Chau <alexchau@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#801474}
-
Nohemi Fernandez authored
The spinner causes EarlGrey to crash following 'infinite' page wait. Bug: 1116650 Change-Id: I20c808dfe77115ba10ba2da5ea06d60688bf76da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375173 Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Commit-Queue: Sergio Collazos <sczs@chromium.org> Auto-Submit: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#801473}
-
Thomas Lukaszewicz authored
Currently NativeViewHost applies a masking path to the NativeView's layer to achieve the rounded corners effect. Tbis CL updates the API to use gfx::RoundedCornersF and uses the rounded corners layer fast path for Aura platforms. Bug: None Change-Id: I038d7b01f315e930cd2577d1c6b4f5dc7f6ca5c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2371309Reviewed-by:
-
Xiaocheng Hu authored
Bug: 964333 Change-Id: I4388432ab6651ef64fa9fcd6b23e687069e6979c NoTry: True Tbr: apotapchuk@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375934Reviewed-by:
-
Peter Boström authored
This tears down DialogModel by through model_.reset() to simulate dialog closing being synchronous. This gives simpler lifetimes for client code as a synchronous delete is more predictable than an asynchronous task from GetWidget()->Close() on its own which is asynchronous. Note that from an implementation perspective the Widget teardown is not synchronous, but this should not be a concern of DialogModel client code. Bug: 1106422 Change-Id: Ib35ec2389e78459ae98a4f901a35858a7fe97189 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2372929Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
-
Lei Zhang authored
In https://crrev.com/651373, the package_exists() implementation changed but the comment did not reflect this change. Change-Id: Ic13e7a3cef28a980ebd167af1bab31006bbf5b59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375928Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#801469}
-
Muyao Xu authored
MediaRouterViewsUI is not dependent on ui/views/view.h and can be moved to c/b/u/ directory. Also renamed the class to MediaRouterUI. Bug: 1116045 Change-Id: I222f5b194b7e707602feb53221ba9e6ec8b35a8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354414 Commit-Queue: Muyao Xu <muyaoxu@google.com> Reviewed-by:
-
RJ Ascani authored
The FuchsiaCdmManager needs a FilePath to write CDM user data to. The Fuchsia ContextProvider receives the persistent directory via the CreateContextParams::cdm_data_directory field. This CL takes the cdm_data_directory and mounts it to /cdm_data. This path is provided to the FuchsiaCdmManager, which does not use it yet. Bug: 991723, b/162078899 Change-Id: I8c6ba6236deb936f743fb70a7f22779e0d3802c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2330811 Commit-Queue: RJ Ascani <rjascani@google.com> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#801467}
-
Vladimir Levin authored
This patch removes ScheduleAnimation calls from lock/unlock. These are not required because we invalidate paint anyway so the lifecycle will already happen. Either that or we are already in the lifecycle when we determine that we need to lock. R=chrishtr@chromium.org, szager@chromium.org Change-Id: I1284b435882e2365f75b1b8baaf79fab8713ba99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375069Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#801466}
-
Weilun Shi authored
Fix a typo in PRESUBMIT.py and sort th |HISTOGRAMS_XMLS_RELATIVE| because different OSes have different file system which introduces non-deterministic into the output of _FindHistogramsXmlFiles() . Bug: 1116807 Change-Id: I8ff36de29464d388f012864155028a77fdb44e6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2372775Reviewed-by:
-
Koji Ishii authored
This test once timed out if LayoutNG and VizDisplayCompositor were enabled. This seems to pass on the current bot. This patch tries to reenable. Bug: 959261 Change-Id: I818fcc015f9e6254fa7f8c17588d6406efeabe67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354375Reviewed-by:
David Tseng <dtseng@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#801464}
-
chromium-internal-autoroll authored
Release_Notes:http://go/help_app-x20/relnotes/Nightly/help_app_nightly_202008250800_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/q7fJGoUZfsUaMt-ae3SViUsR1NdBaXcLVuaNOAI_8CMC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll Please CC help-app@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: help-app@grotations.appspotmail.com Change-Id: I81f2aca91d47a911af36225de7e3ec04b10ae617 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375446Reviewed-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@{#801463}
-
Alexander Cooper authored
Now that the OpenXR runtime has been shipped for a while, and WMR has been updated to interface with OpenXR in a frictionless manner, we would like to unify OpenXR as the single runtime that supports WebXR. Given that WMR support has shipped, rather than delete the runtime immediately, we will first disable it, and see if any issues arise. However, given that almost all WebXR sessions on desktop go through OpenXR, we don't expect any issues. Bug:1121624 Change-Id: I2276f8a5a5954e09276a44b2cfcaf8ad10747100 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373393Reviewed-by:
Brandon Jones <bajones@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#801462}
-
Victor Vianna authored
Fix style consistency in the file. Change-Id: Ib43e942e8acc3a551c9f224a791ef641b55b794d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375425Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/master@{#801461}
-
