Google Git
Sign in
chromium / chromiumos / platform / reporting / refs/heads/upstream/master
commit390dbb979502274371301f7fcc87d1aab60a18e0[log] [tgz]
authorJosh Hilke <jrhilke@google.com>Fri Apr 26 05:16:17 2024
committerCopybara-Service <copybara-worker@google.com>Fri Apr 26 05:31:36 2024
tree274c29e3157fa9003180737085afa5d35fe4780c
parent87271f09e6248b37f0d46c6b502f3273addc5ffd [diff]
Add Chrome crash observer to metric reporting manager.

Add a fatal chrome crash observer to the metric reporting manager which
sends fatal chrome crashes to a new destination: CHROME_CRASH_EVENTS.

DanglingUntriaged-notes: just updating unit test
Change-Id: Ieee2effa58edf2e5049b535aea6c5e981cd6dcad
Bug: b:332614580
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5478414
Commit-Queue: Josh Hilke <jrhilke@google.com>
Reviewed-by: Alberto Juarez <albertojuarez@google.com>
Reviewed-by: Leonid Baraz <lbaraz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1292866}
NOKEYCHECK=True
GitOrigin-RevId: 14309272ee0b371dcb46a1766bbe9541a5943606
1 file changed
tree: 274c29e3157fa9003180737085afa5d35fe4780c
  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.