Google Git
Sign in
chromium / chromium / src / components / reporting / 3543d639e3c8e83cb1039bc3a9c338696346c416
commit3543d639e3c8e83cb1039bc3a9c338696346c416[log] [tgz]
authorDavid Benjamin <davidben@chromium.org>Fri Jun 28 18:15:02 2024
committerCopybara-Service <copybara-worker@google.com>Tue Jul 02 07:02:09 2024
treebc82d035dc991bcdd00eb2e67c7036fe30a96201
parent866830ff7193450e217c1770a3ea448e200989e4 [diff]
Remove now unnecessary EnsureOpenSSLInit and CRYPTO_library_init calls

BoringSSL now initializes itself internally, so there is no need to
initialize it before calling into it. (In fact, CRYPTO_library_init is
now a no-op.)

Fixed: 348923058
Change-Id: I09a69c3d1f76f9ac3eb7c93bae225f188a008205
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5650103
Reviewed-by: Brando Socarras <brandosocarras@google.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Mark Rowe <markrowe@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Jon Mann <jonmann@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1321077}
NOKEYCHECK=True
GitOrigin-RevId: 0a02b73e8c3116ca8ee07c5ccc8c7a656099de01
2 files changed
tree: bc82d035dc991bcdd00eb2e67c7036fe30a96201
  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.