> I thought the purpose of mozregression was, essentially, to automate the process of download and running nightlies, which I just completed - that's how I got those GOOD/BAD nightlies from the prior comment.
It can and should by default drilldown into *the individual commit level*, not just the Nightly release. There can be hundreds of changes per Nightly so it doesn't necessarily narrow down things enough.
Bug 1769845 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> I thought the purpose of mozregression was, essentially, to automate the process of download and running nightlies, which I just completed - that's how I got those GOOD/BAD nightlies from the prior comment.
It can and should by default drilldown into *the individual commit level*, not just the Nightly release. There can be hundreds of changes per Nightly so it doesn't necessarily narrow down things enough to just get the data range (we have another report of this problem and approximate date range but are still baffled at the cause).
> I thought the purpose of mozregression was, essentially, to automate the process of download and running nightlies, which I just completed - that's how I got those GOOD/BAD nightlies from the prior comment.
It can and should by default drilldown into *the individual commit level*, not just the Nightly release. There can be hundreds of changes per Nightly so it doesn't necessarily narrow down things enough to just get the date range (we have another report of this problem and approximate date range but are still baffled at the cause).
> I thought the purpose of mozregression was, essentially, to automate the process of download and running nightlies, which I just completed - that's how I got those GOOD/BAD nightlies from the prior comment.
It can and should by default proceed from a date range to eventually drill down into *the individual commit level*, not just the Nightly release. There can be hundreds of changes per Nightly so it doesn't necessarily narrow down things enough to just get the date range (we have another report of this problem and approximate date range but are still baffled at the cause).
> I thought the purpose of mozregression was, essentially, to automate the process of download and running nightlies, which I just completed - that's how I got those GOOD/BAD nightlies from the prior comment.
It can and should by default proceed from a date range to eventually drill down into *the individual commit level*, not just the Nightly release. There can be hundreds of changes per Nightly so it doesn't necessarily narrow down things down enough if we just get the date range (we have another report of this problem and approximate date range but are still baffled at the cause).
> I thought the purpose of mozregression was, essentially, to automate the process of download and running nightlies, which I just completed - that's how I got those GOOD/BAD nightlies from the prior comment.
It can and should by default proceed from a date range to eventually drill down into *the individual commit level*, not just the Nightly release. There can be hundreds of changes per Nightly so it doesn't necessarily narrow down things down enough if we just get the date range (we have another report of this problem and approximate date range but are still baffled at the cause).
i.e. once mozregression knows the range of Nightlies, it will move on to our CI and start bisecting all the Firefox changes made that day.