QA/Automation/Projects/WebRTC/Crashtest Guide: Difference between revisions

QA/Automation/Projects/WebRTC/Crashtest Guide (view source)

Revision as of 12:47, 13 December 2012

49 bytes removed , 13 December 2012

→‎Building the debug

Nebelhom

Confirmed users

35

edits

@@ Line 79: / Line 79: @@
 Now run the following command from the command line
------------------------------------------------
+    (home):~/path/to/dir$ patch -p1 -R < %filename%
-(home):~/path/to/dir$ patch -p1 -R < %filename%
------------------------------------------------
 as an example, I ran in this case  patch -p1 -R < revert-patch-bug-803535.patch  however the file can be called whatever you want.
-SIDE NOTE:
+{| border="1" cellpadding="5"
+|'''SIDE NOTE:'''<br>
 In order to revert this change call either hg revert –all or patch -p1 < %filename% .
 It might also be wise to make sure at this point that the changes were truly implemented.
+|}
+<br>
 Now it is time, to (re-)build our firefox debug build. To do this, call the following from command line
---------------------------
+    nice -19 make -f client.mk
-nice -19 make -f client.mk
---------------------------
 This should only take a couple of minutes given that we are only changing a couple of files from the previous build. The time taken to build this, however, may take longer depending on the amount of changes that were made since then.
-SIDE NOTE:
+{| border="1" cellpadding="5"
+|'''SIDE NOTE:'''<br>
 If the building process takes a very long time, you may want to consult the following websites to potentially adjust the running time:
-https://developer.mozilla.org/en-US/docs/Developer_Guide/Mozilla_build_FAQ#Making_builds_faster
+*https://developer.mozilla.org/en-US/docs/Developer_Guide/Mozilla_build_FAQ#Making_builds_faster
+*https://developer.mozilla.org/en-US/docs/Developer_Guide/mach
-https://developer.mozilla.org/en-US/docs/Developer_Guide/mach
+|}
 ===Check the testcase in the debug===