On Tue, Oct 14, 2014 at 8:48 AM, Gregory Szorc wrote:
> On 10/13/14 12:17 PM, Benjamin Smedberg wrote:
>>
>> tl;dr: I have a tool for generating regression-range links from
>> buildids. http://bsmedberg.github.io/firefox-regression-range-finder/
>>
>> Often times when we're investigating regressio
On 10/13/14 12:17 PM, Benjamin Smedberg wrote:
tl;dr: I have a tool for generating regression-range links from
buildids. http://bsmedberg.github.io/firefox-regression-range-finder/
Often times when we're investigating regressions (crashes, etc), we have
the build ID of the nightly where the regr
On Monday 2014-10-13 15:17 -0400, Benjamin Smedberg wrote:
> it's not the easiest thing in the world to turn that into an actual
> pushlog link which lists the commits in the regression range.
Just a reminder: I expect many of you know this already, but I
think it's worth repeating: if you're us
On 10/13/2014 6:03 PM, Mike Hommey wrote:
On Mon, Oct 13, 2014 at 03:17:44PM -0400, Benjamin Smedberg wrote:
tl;dr: I have a tool for generating regression-range links from buildids.
http://bsmedberg.github.io/firefox-regression-range-finder/
Often times when we're investigating regressions (c
On Mon, Oct 13, 2014 at 03:17:44PM -0400, Benjamin Smedberg wrote:
> tl;dr: I have a tool for generating regression-range links from buildids.
> http://bsmedberg.github.io/firefox-regression-range-finder/
>
> Often times when we're investigating regressions (crashes, etc), we have the
> build ID o
tl;dr: I have a tool for generating regression-range links from
buildids. http://bsmedberg.github.io/firefox-regression-range-finder/
Often times when we're investigating regressions (crashes, etc), we have
the build ID of the nightly where the regression started. But it's not
the easiest thin
6 matches
Mail list logo
