[flutter_tools] increase windows tool_integration_tests shard#95917
Conversation
.ci.yaml
Outdated
There was a problem hiding this comment.
This unfortunately still shows some of the pain with having to roll into the LUCI configs. We need to duplicate these builders with bringup: true, then land a separate commit to remove the label
Once we move flutter/infra to a generic builder we can get around this
There was a problem hiding this comment.
You mean leave tool_integration_tests_1_5 as blocking and add tool_integration_tests_1_6 as bringup? and then after it rolls to the builder config, delete the old ones and mark the new ones as blocking?
There was a problem hiding this comment.
Yes. Post-submit will seem like there are duplicates, which is fine.
goderbauer
added
c: contributor-productivity
christopherfujino
force-pushed
the
increase-window-tool-integration-shard
branch
from
66e0577 to
64db7ff
Compare
|
@CaseyHillers could you take another look? CI failures are unrelated CDN network failures: #96550 |
…ool-integration-shard
4 participants
increase windows tool_integration_tests shards from 5 -> 6 to fix #95584 (tests are just at the timeout limit now)