| commit | 8c4c29ede5514765c04a4c29db42ca3bb6b62b85 | [log] [tgz] |
|---|---|---|
| author | Kendal Harland <kjharland@fuchsia.infra.roller.google.com> | Fri Aug 11 18:28:44 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Aug 11 11:29:57 2023 -0700 |
| tree | 85d0c7cf55e166797aa93df6518d39adea3641b2 | |
| parent | dead72af2217aef0eaa1aae5effd92f32d58f63d [diff] |
[roll] Roll fuchsia [diagnostics] Refactor detect tests to use TRP The tests connect to a test realm factory that launches triage-detect.cm with mocks for these capabilities: - fuchsia.feedback.CrashReporter - fuchsia.feedback.CrashReportingProductRegister - directory /config/data. Previously the test "spied" on the detect component's egress FIDL traffic using process local message passing (mpsc). These messages are now one-way FIDL events emitted from the realm factory server. Some test failure modes are more explicit: - Test cases can expect the triage-detect component to bail early by asserting that a OnBail event appears in the set of expected events, rather than setting a separate boolean `bails` option. - The exact set of expected diagnostics fetches is represented in the set of expected events. - There are no separate streams for “done” and “error” events sent from the test realm. Errors are hard failures and "done" is now a test event. Overall this makes comparing the set of expected events much simpler because expectations are expressed completely by the test data - for example if a crash should not appear first in the set of the events, the test data says so. Original-Bug: b/291940118 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/857857 Original-Revision: d09ca962197ca2e5d280e9a6bad51bb646cf138b GitOrigin-RevId: e8be04ce75a2449edd096fd95506fc790811c328 Change-Id: I92845c7632b78fa15b5d9afaaff0ddcb3e2eb972
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.