-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
P2A bug or feature request we're likely to work onA bug or feature request we're likely to work onarea-buildUse area-build for SDK build issues.Use area-build for SDK build issues.type-enhancementA request for a change that isn't a bugA request for a change that isn't a bug
Description
I have landed several changes into dart-lang/sdk, which have each ultimately caused some bot somewhere to fail, as each change causes one or most customer tests to fail in the flutter/tests repo. There is no trybot for these "flutter customer tests."
This current feedback loop is very expensive for me and for the flutter engine rollers:
- it takes several days for me to find out the change causes new failures in flutter/tests
- it breaks some flutter auto-roller or other
- breaking the auto-roller requires humans to identify the culprit, and revert my change
- I must fix each customer's codebase to be compatible with my change
- I must bump the commit SHA of each customer's codebase in flutter/tests
- I land again, without any customer test trybots, cycling back to the top of this feedback loop.
CC @Hixie @jason-simmons @iskakaushik to perhaps fill in details I got wrong above
kallentu, keertip and jacob314
Metadata
Metadata
Assignees
Labels
P2A bug or feature request we're likely to work onA bug or feature request we're likely to work onarea-buildUse area-build for SDK build issues.Use area-build for SDK build issues.type-enhancementA request for a change that isn't a bugA request for a change that isn't a bug