One thing that would help us keep the tree more green is avoiding compile
failures. A compile failure is very bad, because without binaries the tests
can't run, and then we have to wait for all of them to run, which may reveal
additional failures etc.
I'm actually surprised by some failures on buildbot, but at least one thing
was not surprising for me: Windows Release compile failures when the Debug
compiles fine (because we don't have Release trybot).
What do you think? Do you have any ideas how we could avoid more compile
failures, even if they are not possible to apply now due to lack of
resources? (for example adding trybots, which seems to not happen soon).
I was also thinking about allowing simple check-ins when the tree is
"waiting for cycle" state (when the sheriff wants to verify that bots cycle
green after a lot of redness). The status would say ("Tree closed, waiting
for cycle; ask sheriff to commit a simple change"), or maybe some
abbreviation for that. It would help people getting code in, and the sheriff
could require really a lot from that change (like full green trybot pass
etc). What do you think about that (especially sheriffs)?
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
