Add `OsUpdateEventObserver` for event based log upload `OsUpdateEventObserver` will observe `reporting::OsUpdatesReporter` and upload logs when an OS update failure is detected. Add observer class to `OsUpdatesReporter`. `OsUpdatesReporter` will create an upload ID and notify the observers if the detected event is failure. Add new `upload_id` field to `OsEventsRecord` proto to connect the log upload and the reporting event on the server side. Add a getter to `DeviceCloudPolicyManagerAsh` to attach the observer. Separate `EventBasedLogUpload` into the virtual interface and Impl class for testing purposes. Use a `MockEventBasedLogUpload` when testing `OsUpdateEventObserver`. `EventBasedLogManager` will initialize and own `OsUpdateEventObserver` instance. Convert `EventBasedLogManagerTest` into a browser test because `OsUpdateEventObserver` needs browser environment to be created. Bug: b/330675033 Change-Id: I52a039af65481dc573500ea954ac9d2c896de9fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5633418 Commit-Queue: Irem Uguz <iremuguz@google.com> Reviewed-by: Simon Hangl <simonha@google.com> Reviewed-by: Alberto Juarez <albertojuarez@google.com> Reviewed-by: Igor <igorcov@chromium.org> Cr-Commit-Position: refs/heads/main@{#1316484}
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.