commit | 0c5f420499426d6c13035124870aee08b76fc447 | [log] [tgz] |
---|---|---|
author | Jason Ling <jasonling@google.com> | Fri Jul 12 21:35:12 2024 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 12 21:54:57 2024 |
tree | 7f3c9126235156e224b5cce2ce7bb41a77b00a63 | |
parent | 3352939d528a67b8fea0a3504f22cf5ccfe84271 [diff] |
Add CROS_SECURITY_FILE to destination File events correspond to read, modify on sensitive files as well as mount and unmount operations. Bug: b:343986520 Change-Id: I7012a2bc9b65b196427f74487d166d2f85e50b88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5703540 Reviewed-by: Alberto Juarez <albertojuarez@google.com> Reviewed-by: Leonid Baraz <lbaraz@chromium.org> Commit-Queue: Jason Ling <jasonling@chromium.org> Auto-Submit: Jason Ling <jasonling@chromium.org> Cr-Commit-Position: refs/heads/main@{#1327021} NOKEYCHECK=True GitOrigin-RevId: b89199f8a259b586f6e69f5ca21bfe7bbb118e7a
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.