commit | 17922695061dc53792027e21172dda7c355af4f9 | [log] [tgz] |
---|---|---|
author | Chong Gu <chonggu@google.com> | Tue Dec 07 19:03:50 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 07 19:03:50 2021 |
tree | 841ebfb7a429a70af57043f84ecac772c0b31195 | |
parent | 61cc5663796ddadefc8228e5d821f25590aaca70 [diff] |
Revert "[fuchsia] Add support for building and running CFv2 tests." This reverts commit f96d3fec83431ec21e8fcdf658a8044b5fb2b144. Reason for revert: Causing infra flakes as described in https://crbug.com/1277536 Original change's description: > [fuchsia] Add support for building and running CFv2 tests. > > No tests use it yet, but the plumbing largely works. > > - The main test() template in //testing/test.gni now allows test targets > to opt-in to CFv2 packaging via the `use_cfv2` boolean variable. This > produces a .cml manifest and generates a runner script that enables > CFv2 processing for test execution. > > - test_runner.py now takes a --component-version=2 switch to indicate > that a test package is a CFv2 package. This switch is added to the > generated runner script via the fuchsia_test_runner template when > `use_cfv2` is specified on a test target. > > - common_args.py now parses --component-version=N from the command line. > > - test_runner.py now handles extracting generated files from a test run > using two strategies based on the component version. For CFv1 > components, files continue to be copied off of the device/emulator via > scp. For CFv2 components, ffx takes care of fetching the files into a > temporary output directory, so test_runner.py need only copy the files > into the caller's desired location. > > - run_test_package.py runs CFv2 tests via `ffx test run`, and uses the > new experimental structured output feature to retrieve generated files > from the test executable. > > - ffx requires networking, so fvdl_target.py now enables networking in > the emulator by default. net_unittests opts out of this for now. > > Bug: 1256502 > Change-Id: Ic9ac5d8e41274a19e06c4166fa2545525b6ec963 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3234526 > Commit-Queue: Greg Thompson <grt@chromium.org> > Reviewed-by: Benjamin Lerman <qsr@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@google.com> > Cr-Commit-Position: refs/heads/main@{#948883} Bug: 1256502, 1277536 Change-Id: Ibb255532f49386cd3a55cb44e792efff4fe464d8 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3321403 Reviewed-by: Zijie He <zijiehe@google.com> Reviewed-by: David Dorwin <ddorwin@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Chong Gu <chonggu@google.com> Auto-Submit: Chong Gu <chonggu@google.com> Reviewed-by: Dirk Pranke <dpranke@google.com> Commit-Queue: Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/main@{#949079}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.