chore: Remove is_fusion from recipes/engine_v2/tester_engine.

Removes at best unused code, and at worst, blindspots for bugs as many of our tests across flutter/recipes exclusively refer to the engine repo, even though it no longer exists.

This CL assumes this recipe only runs in flutter/flutter.

Change-Id: Ibd00d1e3f94b2397f4aca672c9e53ee256125769
Bug: https://github.com/flutter/flutter/issues/170843
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66744
Reviewed-by: Jason Simmons <jsimmons@google.com>
Commit-Queue: Matan Lurey <matanl@google.com>
3 files changed
tree: b4661304f962acb4c5bc00d02893065125ab07ef
  1. .vscode/
  2. infra/
  3. recipe_modules/
  4. recipes/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. CONTRIBUTING.md
  9. LICENSE
  10. OWNERS
  11. README.md
  12. recipes.py
README.md

Flutter LUCI Recipes

This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.

Supported repositories roll their .ci.yaml into flutter/infra, which updates what properties builds have. For example, flutter config specifies various dependencies the different tests require, which are then used by the flutter_deps recipe_module No modifications to flutter/infra are required to work on the recipes.

Contributing

Please follow instructions on Contributing docs to set up your development environment.