Google Git
Sign in
chromium / chromium / src / components / reporting / 47117ab7afdca65836def11e62063a3d1ffadf32
commit47117ab7afdca65836def11e62063a3d1ffadf32[log] [tgz]
authorShanthanu Bhardwaj <xanth@google.com>Tue Sep 09 21:19:20 2025
committerCopybara-Service <copybara-worker@google.com>Tue Sep 09 21:26:42 2025
tree167ca70606d7c15460c685674206d29fb107d07b
parent877d0beed701e6d58be98b7037b06052d1254dd4 [diff]
Add full proto runtime targets for UploadEventsRequest and transitive deps We log these values in the chrome://safe-browsing page and need full targets to represent the proto targets in a human-readable way. Change-Id: I6d6c9cbb37dff55264c115896052871122f74508 Bug: 394403142 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6922749 Reviewed-by: Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by: Vignesh Shenvi <vshenvi@google.com> Commit-Queue: Shanthanu Bhardwaj <xanth@google.com> Cr-Commit-Position: refs/heads/main@{#1513318} NOKEYCHECK=True GitOrigin-RevId: df8c43337b1503ec09b7a4ae852e5e2eece560d9
1 file changed
tree: 167ca70606d7c15460c685674206d29fb107d07b
  1. client/
  2. compression/
  3. encryption/
  4. health/
  5. metrics/
  6. proto/
  7. resources/
  8. storage/
  9. util/
  10. DIR_METADATA
  11. OWNERS
  12. PRESUBMIT.py
  13. README.md
README.md

The Encrypted Reporting Pipeline (ERP) provides a universal method for upload of data for enterprise customers.

The code structure looks like this:

Chrome:

  • //components/reporting
    Code shared between Chrome and ChromeOS.
  • //chrome/browser/policy/messaging_layer
    Code that lives only in the browser, primary interfaces for reporting data such as ReportQueueImpl and ReportQueueConfiguration.

ChromeOS:

  • //platform2/missived
    Daemon for encryption and storage of reports.

If you'd like to begin using ERP within Chrome please check the comment in //components/reporting/client/report_queue_provider.h.

Run Unit Tests

To run the unit tests for this directory, after having configured Chromium's build environment:

  1. Run autoninja -C out/Default components_unittests to build the components unit test executable.

  2. Then, run out/Default/components_unittests --gtest_filter='<target tests>' to run relevant tests. Here, <target tests> is a wildcard pattern (refer to the document of gtest for more details). For example, to run all tests for StorageQueue, run

    $ out/Default/components_unittests --gtest_filter='*/StorageQueueTest.*'

    For another example, to run all tests in this directory, run

    $ tools/autotest.py -C out/Default --run_all components/reporting

    You can also append a filter such as --gtest_filter='*/StorageQueueTest.*' to the line above.

    Another useful flag for dealing with flaky tests is --gtest_repeat=, which repeats tests for multiple times.

    For more gtest features, check out the gtest document.