QA/Platform/Graphics/Guides - Revision history

Ashughes: /* Finding a Regression Window */

2015-12-03T19:34:44Z

Finding a Regression Window

← Older revision		Revision as of 19:34, 3 December 2015
Line 1:		Line 1:
	= Finding a Regression Window =		= Finding a Regression Window =
	~~== Installing Mozregression ==~~
	~~Instructions for Windows:~~
	* Download and install [http://www.activestate.com/activepython/downloads Python 2.7]
	* Open a Windows command window (Run cmd.exe)
	* Execute this command: <pre>pip install -U mozregression</pre>
	* Confirm mozregression is installed by executing this command: <pre>mozregression --version</pre>
	* If you get stuck, see the full instructions [http://mozilla.github.io/mozregression/install.html here]

	== How Mozregression Works ==		== How Mozregression Works ==
	Mozregression works by downloading Firefox Nightly builds from a range of dates allowing you to easily narrow down the first Nightly which introduced a bug. Once a Nightly is downloaded and installed, Mozregression will start Firefox with a temporary profile and allow you to test your bug. After testing the bug, you give Mozregression a ''good'' or ''bad'' command and it will split the range in half, downloading the next build. Once the range has been narrowed down to a single day it will give you a pushlog for the build that will identify the changes which may have caused the bug. This should be attached to the bug report.		[http://mozilla.github.io/mozregression/install.html Mozregression] works by downloading Firefox Nightly builds from a range of dates allowing you to easily narrow down the first Nightly which introduced a bug. Once a Nightly is downloaded and installed, Mozregression will start Firefox with a temporary profile and allow you to test your bug. After testing the bug, you give Mozregression a ''good'' or ''bad'' command and it will split the range in half, downloading the next build. Once the range has been narrowed down to a single day it will give you a pushlog for the build that will identify the changes which may have caused the bug. This should be attached to the bug report.

	As mentioned above, the range will first be narrowed down to a particular Nightly build, then continue to an Inbound build, which will often get us down to a single patch. After the Nightly build search is done, mozregression will note the range for it, then continue to bisect the Inbound builds. When recording the results of mozregression, it is useful to record the Nightly range as well, even if the Inbound range is found.		As mentioned above, the range will first be narrowed down to a particular Nightly build, then continue to an Inbound build, which will often get us down to a single patch. After the Nightly build search is done, mozregression will note the range for it, then continue to bisect the Inbound builds. When recording the results of mozregression, it is useful to record the Nightly range as well, even if the Inbound range is found.

Ashughes: /* Using Mozregression */

2015-05-07T16:10:10Z

Using Mozregression

← Older revision		Revision as of 16:10, 7 May 2015
Line 26:		Line 26:
	* ''good'' if the build does not reproduce the bug		* ''good'' if the build does not reproduce the bug
	* ''skip'' if you want to skip testing the bug in that build		* ''skip'' if you want to skip testing the bug in that build
	* ''broken'' if the build does not work ~~at all (eg. if it crashes)~~		* ''broken'' if the build does not work and you're unable to test your bug

	4) Mozregression will bisect the range and grab the next nightly, repeating the process above		4) Mozregression will bisect the range and grab the next nightly, repeating the process above

Ashughes: /* Using Mozregression */

2015-05-07T16:03:59Z

Using Mozregression

@@ Line 16: / Line 16: @@
 '''''Note: We recommend [[#Narrowing_the_Range|narrowing down the range]] manually before using mozregression.'''''
-If you don't know the dates, simply run ''mozregression'' from a terminal/command window. This will download Firefox Nightly builds starting from January 1, 2009. However, you can save yourself some time and hassle if you give mozregression a narrower range. You may find some of the really old builds will just fail to work, especially on newer platform versions.
+Using mozregression is as simple as running ''mozregression'' from a command prompt. However, this will start with Nightly builds from January 1, 2009 which could make finding the regression range a longer process. Assuming you know the build dates for the first bad and last good Nightly you would run ''mozgression --good YYYY-MM-DD --bad YYYY-MM-DD'' where YYYY-MM-DD is the date of each build. See [[#Narrowing_the_Range|narrowing down the range]] for information on getting those dates.
-If you know the dates, simply run ''mozgression --good YYYY-MM-DD --bad YYYY-MM-DD'' where good is the date of the last build you know is good and bad is the date of the first build you know is bad.
+) Open a command prompt and run ''mozgression --good YYYY-MM-DD --bad YYYY-MM-DD'' where YYYY-MM-DD is the range of dates you want to test.
 == Narrowing the Range ==

Ashughes: /* Narrowing the Range */

2015-05-07T15:45:18Z

Narrowing the Range

← Older revision		Revision as of 15:45, 7 May 2015
Line 23:		Line 23:
	'''''Note: We recommend narrowing down the range to six weeks between builds before using mozregression.'''''		'''''Note: We recommend narrowing down the range to six weeks between builds before using mozregression.'''''

	* Start ~~from~~ the ~~date of~~ the build you ~~reproduced~~ the bug ~~with~~		1) Start by getting the Build ID for the Firefox build with which you're reproducing the bug
	* Open the ''about:support'' page ~~and make note of the Build ID from~~ the ''Application Basics'' section (the build ~~ID follows~~ a YYYYMMDDhhmmss format).		* Open the ''about:support'' page
	* Install a build from six weeks before that date from [ftp://ftp.mozilla.org/pub/firefox/nightly/ ftp.mozilla.org]		* Scroll down to the ''Application Basics'' section
	* If that build reproduces the bug~~, go~~ back another six weeks		* Make note of the ''Build ID'' as the "first bad" build (it's a string of numbers in YYYYMMDDhhmmss format)
	* Repeat this process until you find a build that does not reproduce the bug ~~and make~~ note of ~~its~~ build ~~date~~
	* ~~Use these dates to~~ run mozregression		2) Install a build from six weeks before that date
			* Go to ftp://ftp.mozilla.org/pub/firefox/nightly/
			* Go to the folder for the year
			** For example, the Firefox Nightly builds from 2015 are at ftp://ftp.mozilla.org/pub/firefox/nightly/2015
			* Go to the folder for the month
			** For example, the Firefox Nightly builds from April 2015 are at ftp://ftp.mozilla.org/pub/firefox/nightly/2015/04/
			* Go to the folder for the mozilla-central build from the day
			* Download the installer for the platform you want
			** For example, the Firefox Nightly 40.0a1 win32 build for April 16, 2015 is at ftp://ftp.mozilla.org/pub/firefox/nightly/2015/04/2015-04-16-03-02-09-mozilla-central/firefox-40.0a1.en-US.win32.installer.exe
			* Run the installer, start Firefox, and try to reproduce the bug

			3) If that build reproduces the bug
			* Make note of the Build ID as the "first bad" build
			* Repeat step 2 going back another six weeks

			4) Once you find a build that does not reproduce the bug
			* Make note of the Build ID as the "last good" build
			* You can now run mozregression and give it the good/bad dates based on the build IDs you noted

	For example, if the build ID of a good build is 20150401123456 and the build ID of a bad build is 20150410123456:		For example, if the build ID of a good build is 20150401123456 and the build ID of a bad build is 20150410123456:

Msreckovic: /* How Mozregression Works */ Add more details on Inbound vs. Nightly

2015-04-14T15:30:30Z

How Mozregression Works: Add more details on Inbound vs. Nightly

← Older revision		Revision as of 15:30, 14 April 2015
Line 10:		Line 10:
	== How Mozregression Works ==		== How Mozregression Works ==
	Mozregression works by downloading Firefox Nightly builds from a range of dates allowing you to easily narrow down the first Nightly which introduced a bug. Once a Nightly is downloaded and installed, Mozregression will start Firefox with a temporary profile and allow you to test your bug. After testing the bug, you give Mozregression a ''good'' or ''bad'' command and it will split the range in half, downloading the next build. Once the range has been narrowed down to a single day it will give you a pushlog for the build that will identify the changes which may have caused the bug. This should be attached to the bug report.		Mozregression works by downloading Firefox Nightly builds from a range of dates allowing you to easily narrow down the first Nightly which introduced a bug. Once a Nightly is downloaded and installed, Mozregression will start Firefox with a temporary profile and allow you to test your bug. After testing the bug, you give Mozregression a ''good'' or ''bad'' command and it will split the range in half, downloading the next build. Once the range has been narrowed down to a single day it will give you a pushlog for the build that will identify the changes which may have caused the bug. This should be attached to the bug report.

			As mentioned above, the range will first be narrowed down to a particular Nightly build, then continue to an Inbound build, which will often get us down to a single patch. After the Nightly build search is done, mozregression will note the range for it, then continue to bisect the Inbound builds. When recording the results of mozregression, it is useful to record the Nightly range as well, even if the Inbound range is found.

	== Using Mozregression ==		== Using Mozregression ==

Msreckovic: /* Installing Mozregression */ Add a link to github page

2015-04-14T15:28:13Z

Installing Mozregression: Add a link to github page

← Older revision		Revision as of 15:28, 14 April 2015
Line 6:		Line 6:
	* Execute this command: <pre>pip install -U mozregression</pre>		* Execute this command: <pre>pip install -U mozregression</pre>
	* Confirm mozregression is installed by executing this command: <pre>mozregression --version</pre>		* Confirm mozregression is installed by executing this command: <pre>mozregression --version</pre>
			* If you get stuck, see the full instructions [http://mozilla.github.io/mozregression/install.html here]

	== How Mozregression Works ==		== How Mozregression Works ==

Ashughes: /* Finding a Regression Window */

2015-04-14T00:18:26Z

Finding a Regression Window

← Older revision		Revision as of 00:18, 14 April 2015
Line 61:		Line 61:

	It may be necessary to bisect the range further but that's outside the scope of this document.		It may be necessary to bisect the range further but that's outside the scope of this document.

			= Testing a Try Build =
			TO BE DETERMINED

Ashughes: /* Using Mozregression */

2015-04-14T00:14:47Z

Using Mozregression

← Older revision		Revision as of 00:14, 14 April 2015
Line 11:		Line 11:

	== Using Mozregression ==		== Using Mozregression ==
	''We recommend [[#Narrowing_the_Range\|narrowing down the range]] manually before using mozregression.''		'''''Note: We recommend [[#Narrowing_the_Range\|narrowing down the range]] manually before using mozregression.'''''

	If you don't know the dates, simply run ''mozregression'' from a terminal/command window. This will download Firefox Nightly builds starting from January 1, 2009. However, you can save yourself some time and hassle if you give mozregression a narrower range. You may find some of the really old builds will just fail to work, especially on newer platform versions.		If you don't know the dates, simply run ''mozregression'' from a terminal/command window. This will download Firefox Nightly builds starting from January 1, 2009. However, you can save yourself some time and hassle if you give mozregression a narrower range. You may find some of the really old builds will just fail to work, especially on newer platform versions.

Ashughes: /* Narrowing the Range */

2015-04-14T00:14:06Z

Narrowing the Range

← Older revision		Revision as of 00:14, 14 April 2015
Line 18:		Line 18:

	== Narrowing the Range ==		== Narrowing the Range ==
	'''''Note~~'''~~: A six ~~week range should be sufficient for~~ mozregression ~~to narrow it down further~~.''		'''''Note: We recommend narrowing down the range to six weeks between builds before using mozregression.'''''

	~~We recommend that~~ you ~~try to narrow down~~ the ~~range a bit before using mozregression. Assuming you found a~~ bug ~~using today~~'~~s Firefox Nightly, you would download~~ and ~~install~~ a ~~previous version~~. ~~Our recommendation is to grab~~ a build from six weeks ~~earlier to begin~~. If that build reproduces the bug, go back another six weeks~~, and repeat~~ until you find a build that does not reproduce the bug.		* Start from the date of the build you reproduced the bug with
			* Open the ''about:support'' page and make note of the Build ID from the ''Application Basics'' section (the build ID follows a YYYYMMDDhhmmss format).
			* Install a build from six weeks before that date from [ftp://ftp.mozilla.org/pub/firefox/nightly/ ftp.mozilla.org]
			* If that build reproduces the bug, go back another six weeks
			* Repeat this process until you find a build that does not reproduce the bug and make note of its build date
			* Use these dates to run mozregression

	Make note of the Build ID from the ''Application Basics'' section of the ''about:support'' page. You can get to this page by simply typing ''about:support'' in the URL field and pressing the ENTER key on your keyboard. Alternatively, you can get to this page by clicking the ''Troubleshooting Information'' item from the ''Help'' menu. The build ID follows a YYYYMMDDhhmmss format. Use this to inform mozregression of the date you want to use.		For example, if the build ID of a good build is 20150401123456 and the build ID of a bad build is 20150410123456:
			<pre>mozregression --good 2015-04-01 --bad 2015-04-10</pre>
	For example, if the build ID of a good build is 20150401123456 and the build ID of a bad build is 20150410123456~~, you would run ''~~mozregression --good 2015-04-01 --bad 2015-04-10~~''.~~

	== If Mozregression Fails ==		== If Mozregression Fails ==

Ashughes: /* If Mozregression Fails */

2015-04-14T00:06:13Z

If Mozregression Fails

← Older revision		Revision as of 00:06, 14 April 2015
Line 52:		Line 52:
	* Add this URL to the bug and ask for someone to check it for changes which may have introduced the regression		* Add this URL to the bug and ask for someone to check it for changes which may have introduced the regression

	Once an offending bug has been identified, ~~the general process is to~~ mark your bug as blocking the offending bug ~~and flagging~~ the developer of the offending bug to ~~look in to it~~.		Once an offending bug has been identified, that bug should be flagged:
			* mark your bug as blocking the offending bug
			* flag the developer of the offending bug using the ''needinfo?'' flag

			It may be necessary to bisect the range further but that's outside the scope of this document.