Google Git
Sign in
chromium / chromiumos / platform / reporting / refs/heads/upstream/main
commite7470c0be39734fe181a5e838585c3b1d9fa6ed9[log] [tgz]
authorshvm <shvm@google.com>Thu Jun 26 19:41:48 2025
committerCopybara-Service <copybara-worker@google.com>Thu Jun 26 19:48:21 2025
treef3cf28be4ebaedf77b13ef0853aa67a394d423bb
parent48a27d696e1e19be4692353a7f1b9d75c982b4ad [diff]
Kiosk: Add new user type and profile load for arcvm kiosk

Bug: 388602323
Change-Id: I7249db12f65cb00d5bfb986a9e3ada2e39cd337b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6471170
Auto-Submit: Shivam Sharma <shvm@google.com>
Commit-Queue: Shivam Sharma <shvm@google.com>
Reviewed-by: Anqing Zhao <anqing@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1479380}
NOKEYCHECK=True
GitOrigin-RevId: 040170e8dcdd3dd93133e5d5dd13cce45ec93d26
1 file changed
tree: f3cf28be4ebaedf77b13ef0853aa67a394d423bb
  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.