On 05 November 2013 14:44:27, David Burns wrote:
We appear to be doing 1 backout for every 15 pushes on a rough
average[4].
I've been thinking about this some more - and I believe the ratio is
probably actually even worse than the numbers suggest, since:
* Depending on how the backouts are performed, the backout of several
changesets/bugs are sometimes folded into one commit.
* The 'total commits' figure includes merges & other automated/non-dev
commits.
* Sometimes breakage is fixed in-place with a commit message such as
"Bug 123456 - Followup...", which was still for a landing that broke the
tree, but wouldn't count be counted.
On 05 November 2013 14:57:17, Kyle Huey wrote:
What is your proposal for doing that? What are the costs involved?
For one: devs building/testing locally before pushing. Many cases of
failures would have been caught be just a simple single-platform
build+run of a single directory's worth of tests.
The benefits of this approach are:
* Available local compute time scales linearly with the number of devs
hired, unlike our Tryserver automation.
* Local dep builds are much quicker than Try clobber builds.
I'm hopeful that with the build peer's ongoing overhaul of our build
system, dep build times for an average patch are going to be short
enough that there really is no excuse not to build locally. Add to that
ongoing work on improving mach commands to ease running just a subset of
the tests (for bonus points making use of the applied MQs to guess which
ones), and it really shouldn't be too onerous of a request.
Best wishes,
Ed
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
