| commit | 44cac78dff817c5bab3a190fa0c3a55a1a005318 | [log] [tgz] |
|---|---|---|
| author | Owners Cleanup <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com> | Tue Aug 26 19:06:36 2025 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 26 19:12:36 2025 |
| tree | c414209ec6a185875ee17b00c311cbb0a9622e97 | |
| parent | e87d4bdc46d479628f1e3147a637b404f4e4d639 [diff] |
[owners] Remove lbaraz@chromium.org from components/reporting/OWNERS This suggested change is automatically generated based on group memberships and affiliations. Please approve this change and vote the highest CR. This will keep the OWNERS file tidy. We ask that you do not ignore this change and either approve it if the OWNER is no longer active or deny it if the OWNER is continuing to review CLs (including under a different affiliation). This CL can always be reverted if the understanding changes. If this change is in error, vote the lowest CR value (i.e. reject the CL) and the bot will abandon it. See the owner's recent review activity for context: https://chromium-review.googlesource.com/q/lbaraz@chromium.org To report an issue, file a bug in the Infra>Codereview component. Change-Id: I2acbc93a071639eaa42bbfd6d5fac732e0f493a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6885830 Reviewed-by: Ahmed Nasr <anasr@google.com> Auto-Submit: Owners Cleanup <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com> Commit-Queue: Ahmed Nasr <anasr@google.com> Cr-Commit-Position: refs/heads/main@{#1506688} NOKEYCHECK=True GitOrigin-RevId: fbb43b10f67ebf42f0c16ad653d49f34a2ca9511
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 //chrome/browser/policy/messaging_layer ReportQueueImpl and ReportQueueConfiguration.ChromeOS:
//platform2/missived If you'd like to begin using ERP within Chrome please check the comment in //components/reporting/client/report_queue_provider.h.
To run the unit tests for this directory, after having configured Chromium's build environment:
Run autoninja -C out/Default components_unittests to build the components unit test executable.
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.