commit | cd2155711b378a85cffabd50c12aeb0b99ae1050 | [log] [tgz] |
---|---|---|
author | Josh Hilke <jrhilke@google.com> | Tue Jun 11 01:37:54 2024 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 11 01:55:40 2024 |
tree | fce6f5d7ea158e94294679eed351b4c359a1bf91 | |
parent | c1fc354e2bcf1748ad316835076515bcfedcb7d0 [diff] |
Combine functions in storage_queue.cc. RetryWithDegradation() is a very shallow wrapper for StartRecordsShedding(). This change combines them. Change-Id: Ie77d60bbbf7a319c0f621226e3c8eaa8627758db Bug: b:345285938 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5619273 Reviewed-by: Vignesh Shenvi <vshenvi@google.com> Commit-Queue: Josh Hilke <jrhilke@google.com> Auto-Submit: Josh Hilke <jrhilke@google.com> Commit-Queue: Vignesh Shenvi <vshenvi@google.com> Cr-Commit-Position: refs/heads/main@{#1313177} NOKEYCHECK=True GitOrigin-RevId: 3df641483cc8161335b4530119c8d6bd8694d33a
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.