On 2015-09-14 1:17 PM, Benjamin Smedberg wrote:
Does this command work by downloading nightly/hourly builds (the way mozregression typically works) or by doing local builds at various changesets and getting a local source regression range?
The former. It's basically just a convenience wrapper for mozregression, so you don't have to go to the trouble of installing system python, mucking with virtualenvs or worrying whether you have the latest version all of which proved to be big pain points with platform developers.
We used to do source builds of Mozilla as part of mozregression, but the implementation had some issues and it was proving to be a pain to maintain. We opted to turn it off since the inbound build support allowed you to get much tighter regression ranges than were previously possible.
Now that we're basically in-tree, we might want to reconsider reactivating it with a better implementation. Any feedback on how useful such a thing would be, compared to just using git/hg bisect?
Will _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
