Google Git
Sign in
chromium / chromium / src / components / reporting / b23aeee82026e4c5b71afab51f7176de33cf825f
commitb23aeee82026e4c5b71afab51f7176de33cf825f[log] [tgz]
authorLei Zhang <thestig@chromium.org>Tue Dec 09 02:17:35 2025
committerCopybara-Service <copybara-worker@google.com>Tue Dec 09 02:23:32 2025
tree0f9a970ed62108d3fe7b0fd7f41b97376a145fa6
parent72f67e42b3cc5d4cb2bb4b7a61ce8ad80defb915 [diff]
Remove superfluous <map> includes from //components headers Remove unnecessary includes. Then do IWYU to fix the build. Removal automated with: git ls-files components | grep '\.h$' | xargs grep -l '<map>$' | \ xargs grep -L std::map | xargs grep -L std::multimap | \ xargs tools/add_header.py --remove --header '<map>' Bug: 40318405 Change-Id: I57a66308625c319056c023282c91ee24fcd06794 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7234717 Reviewed-by: Tommy Nyquist <nyquist@chromium.org> Owners-Override: Lei Zhang <thestig@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1555857} NOKEYCHECK=True GitOrigin-RevId: 3a4f9141339792d856a791f88d44693e7cb4b6c9
1 file changed
tree: 0f9a970ed62108d3fe7b0fd7f41b97376a145fa6
  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.