| commit | 369d6fdece31360ef6d4d903645b1af565de6c7e | [log] [tgz] |
|---|---|---|
| author | Rich Kadel <richkadel@fuchsia.infra.roller.google.com> | Tue Mar 08 00:20:57 2022 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 07 16:23:28 2022 -0800 |
| tree | 1a4ee63dc69716485aa830275dec14d2a030f995 | |
| parent | 20c148de9331c09ce8aeef199e5b397710607312 [diff] |
[roll] Roll fuchsia [test_manager] Allow dart/flutter runners and route required services In order to run a CFv2-based Dart test, I developed a Rust realm_builder shim that loads the required runner into the dart component's environment, and eagerly launches the dart test component. Because the Dart-based test requires loading a Dart or Flutter Runner into the environment (and the Runner requires some additional privileges and services not offered to hermetic tests) the test must run as a `system-test` at this time. Also note that it may not (yet) be possible for the test manager to capture the exit status from the Dart test to the test manager. The exit status is typically used to properly report tests passing vs. tests failing. However, with the described Rust realm_builder workaround, test manager does report the test failure if the test logs an error (which the dart::test implementation currently does). Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/652767 Original-Revision: 3c343f6c2829efbaacc2dfcb6a3f7020957ccc24 GitOrigin-RevId: cc301e3abf06933d865d67327056705fbd6322ed Change-Id: I4682be4ed05dd5de88dcf01ca554a1be3a85ad52
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.