Google Git
Sign in
chromium / chromium / src / components / reporting / 72f67e42b3cc5d4cb2bb4b7a61ce8ad80defb915
commit72f67e42b3cc5d4cb2bb4b7a61ce8ad80defb915[log] [tgz]
authorJan Keitel <[email protected]>Fri Dec 05 10:49:40 2025
committerCopybara-Service <[email protected]>Fri Dec 05 10:59:00 2025
tree6c824364cada7d58e84cc2284f468df80bb4ba8d
parentd58cdf45394e25ca66cec73a0ad3ca1825f79ba6 [diff]
Migrate ResourceManagedBuffer to base::HeapArray

This change updates ResourceManagedBuffer to use
base::HeapArray<uint8_t> instead of std::unique_ptr<char[]> for
managing the buffer. It then uses the resulting span-based API to
replace pointer-based file API calls by span-based ones.

No functionality changes.

Bug: 435317390
Change-Id: I72a33db0a6a08394ad4a04ad09cf861e52004c42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7208436
Reviewed-by: Tom Sepez <[email protected]>
Commit-Queue: Jan Keitel <[email protected]>
Reviewed-by: Dominique Fauteux-Chapleau <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1554564}
NOKEYCHECK=True
GitOrigin-RevId: 2f0d85aaad72add1add5f18e69078ead83a7cba4
4 files changed
tree: 6c824364cada7d58e84cc2284f468df80bb4ba8d
  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.