Hi all- I'd like to understand better what the criteria are for a builder to become a "core" builder.
We've been putting lot of effort into keeping the Windows testers green lately (especially the Windows 7 Release (Tests) builder), and it seems like it would be good for them to eventually join the "core" group so they can reap the benefits of sheriffbot, an increased number of people looking at them, etc. Most of the failures that happen on the Windows bots these days are either due to: 1) a new test being added which needs results on Windows 2) an existing test with Windows-specific results being modified without the Windows results being updated 3) test flakiness Being in the "core" group seems like it would help with (1) and (2) because the people who are making these changes would notice that they forgot Windows. It wouldn't help with (3), of course. (We're obviously trying to track down all causes of flakiness we can.) So what does it take for a builder to be a "core" builder? Once we know this, we can hopefully focus our Windows efforts toward satisfying the criteria. Thanks! -Adam _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
