commit | 0a463dc528d0b75da8ebf27850f5945b2ba23f9c | [log] [tgz] |
---|---|---|
author | Ashley Prasad <ashleydp@google.com> | Wed Nov 29 00:49:58 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 29 00:49:58 2023 |
tree | 5acfda4dd4a68e6eca3485e29f399e811f2120c7 | |
parent | eb76ee2b1b2fc0858bc49b68b1204533b456d0cd [diff] |
Reland "audio-settings: Add RenderAudioPage interactive uitest" This is a reland of commit fa83e5663a9386bff3fc1eed79d1051b6276793d Updates lambda functions to take device ID by value instead of passing by reference. Also pass primary active node by value instead of passing in "this" to access primary node lookup function. Original change's description: > audio-settings: Add RenderAudioPage interactive uitest > > Add interactive uitest to replace audioui.RenderAudioPage > tast test. > > Bug: b:307385730 > Test: interactive_ui_tests --gtest_filter=*AudioSettingsInteractiveUiTest* > Change-Id: If661b661b938b7ae1a9af26ac237ca37ce757b64 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5047636 > Reviewed-by: Michael Checo <michaelcheco@google.com> > Commit-Queue: Ashley Prasad <ashleydp@google.com> > Cr-Commit-Position: refs/heads/main@{#1227648} Bug: b:307385730 Test: interactive_ui_tests --gtest_filter=*AudioSettingsInteractiveUiTest* Test: Also, locally ran interactive_ui_tests filtered on AudioSettingsInteractiveUiTest with same gn args as linux-chromeos-asan-rel on repeat which completed successfully. Cq-Include-Trybots: luci.chromium.try:linux-lacros-asan-lsan-rel Change-Id: Ied38ef94a2050528d98d1fc4f7f4ee6eaff7c636 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053668 Reviewed-by: Michael Checo <michaelcheco@google.com> Commit-Queue: Ashley Prasad <ashleydp@google.com> Cr-Commit-Position: refs/heads/main@{#1230346}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.