This documentation describes how to run flutter/flutter presubmit checks on flutter/engine PRs before submitting them.
Step (1) is the usual flutter/engine workflow.
Edit your flutter/flutter checkout as follows:
bin/internal/engine.version
should be edited to contain the commit hash from (2).bin/internal/engine.realm
should be edited to contain the string flutter_archives_v2
.To run flutter/flutter presubmits on CI, you can accomplish these two edits directly in the GitHub editor UI, if desired. Otherwise, upload a flutter/flutter PR with these changes.
You can also build apps, and run tests locally at this point.
The flutter/flutter presubmit checks will run. There will be at least two failures:
engine.realm
file will fail a presubmit check.fuchsia_precache
test will fail because Fuchsia artifacts are not uploaded from Engine presubmit runs.Any other failures are possibly due to the changes to flutter/engine, so deflake and examine them carefully.
A subset of devicelab tests are available for optionally running in presubmit on flutter/flutter PRs. They are the tests listed in the flutter/flutter .ci.yaml file that are prefixed with Linux_android
, Mac_android
, and Mac_ios
.
To run one of these tests, remove the line presubmit: false
from the .ci.yaml
file under the test you'd like to run. For an example, see the PR here.
This will trigger the devicelab test to run. The test will show up in the list of presubmit checks, and you can click through to the LUCI page to see the results.