Auto-tools/Projects/Mozregression: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(mozregression project page)
 
Line 47: Line 47:


https://globau.wordpress.com/2013/10/21/github-pull-requests-and-bugzilla/
https://globau.wordpress.com/2013/10/21/github-pull-requests-and-bugzilla/
Please make sure your patch conforms to [https://www.python.org/dev/peps/pep-0008/ PEP8] before submitting it.

Revision as of 17:35, 16 December 2014

mozregression

Introduction

mozregression is an interactive regression range finder for Mozilla nightly and inbound builds. It uses a binary search algorithm for quickly determining a changeset range corresponding to when a problem was introduced. It is widely use by Mozilla developers and other community members to help find regressions.

See the interactive video on codefirefox.com: http://codefirefox.com/video/mozregression

Homepage: http://mozila.github.io/mozregression

Active contributors

These people are actively working on mozregression and good people to ask questions of (or for review):

How to setup for development

Assuming you have python, git, and virtualenv installed check out the mozregression repository and install it locally inside there. From there, you should be able to modify the code and test your changes. On Linux and MacOS X, this looks like:

 virtualenv mozr
 cd mozr
 source bin/activate
 git clone https://github.com/mozilla/mozregression.git mozregression
 cd mozregression
 pip install -e .

(Windows instructions should be pretty similar, the only different should be the activation step)

Issue / feature tracking

We track mozregression bugs and feature requests inside bugzilla, in the Testing / mozregression component.

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 502 [1] => Bad Gateway ) ) 1


Submitting patches

If a bug is not open already corresponding to the bug you want to fix (or the feature you want to add), please file one. After that, please open a github pull request with your code change, and set a flag in bugzilla for it to be reviewed, as described here:

https://globau.wordpress.com/2013/10/21/github-pull-requests-and-bugzilla/

Please make sure your patch conforms to PEP8 before submitting it.