[roll] Roll fuchsia [fdf] Create DFv2-specific core bot tests

Create buildbot groups `//bundles/buildbot:core_dfv2` and
`//bundles/buildbot:host-tests_dfv2` which are similar to their
counterparts, `core` and `host-tests`, except they do not contain tests
that fail when DFv2 is enabled and using chromebook.

These groups are to be used by the core.x64-dfv2-release and
core.chromebook-x64-dfv2-release builder bots in a future CL so that the
builders can pass and be monitored by the Fuchsia build gardeners.  This
is in order to prevent regressions in DFv2.

Original-Bug: 102234
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/719645
Original-Revision: c4c94ce08cb55104fd066503230161c69209cfda
GitOrigin-RevId: 249a255469ae7fd9a03a59f1ab662d0b0a0b5013
Change-Id: I0f82072a6b0642694425266b0e4651c9c1331ac5
1 file changed
tree: e7d7ecb866b5f92006b989a55c51b1f74272eadd
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.