commit | 62c55ffeaaa28cabdb6fb8eb69e9c8aaec205a69 | [log] [tgz] |
---|---|---|
author | Nikhil Nayunigari <nikhilcn@google.com> | Fri Oct 06 16:10:27 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 06 16:10:27 2023 |
tree | 8161e699b3ea911c93de1512a9ccfd050b4a6a5d | |
parent | 5b83fda4265658f093981d47d9026c45c61f4df4 [diff] |
Reland "[CrOS Hotspot] Add hotspot config to fieldtrial_testing_config" This is a reland of commit 224f46cf5e4b98dc6325d6e70284422049d767c4 This change also fixes an issue that was causing the test DeviceEventLogErrorBrowserTest.LoginUser to fail. Upon login, the newly introduced hotspot code emits a couple of error log statements which was causing the browser test to fail. I've modified those statements to 'event' instead of 'error' as they aren't user impacting. We'll investigate why those were being logged as error and the callback was returned a success status in the first place. Original change's description: > [CrOS Hotspot] Add hotspot config to fieldtrial_testing_config > > This change adds hotspot configuration in fieldtrial_testing_config.json > > Change-Id: Ic3e879c0860816f028427de97cc31cc280543fa6 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4912445 > Reviewed-by: Regan Hsu <hsuregan@chromium.org> > Commit-Queue: Nikhil Nayunigari <nikhilcn@google.com> > Cr-Commit-Position: refs/heads/main@{#1205912} Change-Id: Idc3b2f79ed55ce5664788e057398dd1867540117 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4916208 Commit-Queue: Nikhil Nayunigari <nikhilcn@google.com> Reviewed-by: Chad Duffin <chadduffin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1206449}
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.