I wanted to chime-in and emphasis this: One of the first thing you do when looking at a bug is establish if it's a regression and starting with mozregression right away if it is!
From my experience running mozregression for easily reproduced regressions can be done in about 10 minutes and it really gets the bug going in the right direction. On Mon, Jan 11, 2016 at 7:21 AM, Julien Pagès <j.parko...@gmail.com> wrote: > Hello from Engineering Productivity! Once a month we highlight one of our > projects to help the Mozilla community discover a useful tool or an > interesting contribution opportunity. > > This month’s project is mozregression! > > mozregression helps to find regressions in Mozilla projects like Firefox or > Firefox on Android. It downloads and runs the builds between two dates (or > changesets) known to be good and bad, and lets you test each build to > finally find by bisection the smallest possible range of changesets where > the regression appears. > > You can read more about it on my blog post: > > > https://parkouss.wordpress.com/2016/01/11/mozregression-engineering-productivity-project-of-the-month/ > > > Julien - on behalf of the Engineering Productivity team. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
