You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Enable/disable luci tests in a single file per repository #63437
I was thinking on expanding the json file with an enabled flag. Something similar to the flaky flag but we will also need a way to disable tests from shards.
I was thinking on expanding the json file with an enabled flag. Something similar to the flaky flag but we will also need a way to disable tests from shards.
Thanks. A flag is good to keep the historical builders all the time.
I will start from the builder level. Then move on to the shard level.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
keyonghan commentedon Aug 11, 2020
@godofredoc Please correct me if anything is incorrect.
I guess what needs here is to enable/disable luci tasks in sub-shard level similar to cirrus yaml file.
(on shard level, https://github.com/flutter/flutter/blob/master/dev/try_builders.json would be the source control to enable/disable a builder)
Sub-shards are configured in flutter/infra, but we want to control on repo level. With those manifest files ready in corresponding repos, cocoon will read those manifest before triggering pre-submit tasks. The
subshardsvalue derived from the manifest file will be added to https://github.com/flutter/cocoon/blob/master/app_dart/lib/src/service/luci_build_service.dart#L193 to replace server side configuration.godofredoc commentedon Aug 11, 2020
I was thinking on expanding the json file with an enabled flag. Something similar to the flaky flag but we will also need a way to disable tests from shards.
keyonghan commentedon Aug 12, 2020
Thanks. A flag is good to keep the historical builders all the time.
I will start from the builder level. Then move on to the shard level.
github-actions commentedon Aug 13, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.