Repository navigation
Migrate SDK shards into separate builders #77947
Description
Builders with shards have been consuming extra trigger bots, and waste lots of resources when rerunning (have to rerun all shards even a single subshard fails). Additionally it has caused difficulty to view results via LUCI UI: #64208.
This is tracking the process to separate shards into separate builders.
Try:
- Create separate builder configs for builders (with shards)
- Enable new separate builders in try_builder.json for presubmit
- Remove old builders (with shards) from try_builder.json for presubmit
- clean up configs for old try builders (with shards) (keep for a couple of days before removing, in case failures if not rebased)
Prod:
- Create separate builder configs for builders (with shards)
- Enable new separate builders in prod_builder.json for postsubmit
- Remove old builders (with shards) from prod_builder.json for postsubmit
- clean up configs for old builders (with shards)
Activity
CaseyHillers commentedon Mar 17, 2021
Do we plan to promote the new linux builders to flaky=false before migrating the other platforms?
When we did the devicelab luci migration, one complaint was infra created too many flaky tasks in the build dashboard to make it actionable.
keyonghan commentedon Mar 17, 2021
Since they are stable, here is the pr to remove flakiness: #78483
github-actions commentedon Aug 4, 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.