mirror of
https://github.com/flutter/flutter.git
synced 2026-01-21 05:04:42 +08:00
5dfe7e6d51
A change which sped up hot restart locally caused many of the devicelab measures to regress. I think this is because we do not measure when the isolate is actually "ready", so starting a reload or restart prematurely can cause time spent doing initialization to be registered as part of the reload operation. A fix for this would be to have the framework include some sort of "initialization complete" event ... but it is not clear what the correct trigger would be. Perhaps after the first frame is successfully registered? (9a3a0dc caused the benchmark regression - possibly since we spend less time syncing files now so we start the restart earlier)
This directory contains tools and resources that the Flutter team uses during the development of the framework. The tools in this directory should not be necessary for developing Flutter applications, though of course, they may be interesting if you are curious.
The tests in this directory are run in the framework_tests_misc-*
shards.
Luci builder file
try_builders.json and prod_builders.json contain the supported luci
try/prod builders for flutter.
try_builders.json
It follows format:
{
"builders":[
{
"name":"yyy",
"repo":"flutter",
"taskName":"zzz",
"enabled":true,
"run_if":["a/b/", "c/d/**"]
}
]
}
- enabled(optional):
trueis the default value if unspecified - run_if(optional): will always be triggered if unspecified
prod_builders.json
It follows format:
{
"builders":[
{
"name":"yyy",
"repo":"flutter",
"taskName":"zzz",
"flaky":false
}
]
}
try_builders.json will be mainly used in
flutter/cocoon to trigger/update pre-submit
flutter luci tasks, whereas prod_builders.json will be mainly used in flutter/cocoon
to refresh luci task statuses to dashboard.