Anna Gringauze edf26e756d
Move web integration tool tests to web.shard (#70226)
* Move web integration tool tests to web.shard

Web integration tool tests depend on DDC changes in SDK. This change
moves them to a separate shard and subshard so CI bot configurations
can run them separately.

In particular, with will allow running those tests on dart CI flutter
HHH web bot instead of a non-web one, allowing early detection and easy
classification of issues caused by SDK changes as VM- or Web related.

* Enabled verbose mode for flaky web_tool_tests

* Split out the test changes to be commited first
2020-11-11 15:42:15 -08:00
..

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): true is 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.