Javascript:Hazard Builds: Difference between revisions

Jump to navigation Jump to search
→‎Running the analysis: browser busted on debian/ubuntu
(→‎Running the analysis: browser busted on debian/ubuntu)
Line 14: Line 14:
To run the browser analysis, you must be on a Fedora/RedHat/CentOS linux64 machine and do:
To run the browser analysis, you must be on a Fedora/RedHat/CentOS linux64 machine and do:


  cd <gecko>
   mkdir ~/haz
   mkdir work
   cd ~/haz
   cd work
   python $SRCDIR/testing/mozharness/scripts/spidermonkey_build.py -c developer_config.py -c hazards/common.py -c hazards/build_browser.py --source $SRCDIR
   python ../testing/mozharness/scripts/spidermonkey_build.py -c developer_config.py -c hazards/common.py -c hazards/build_browser.py --source $SRCDIR


It doesn't matter what directory you run from, as long as it's not at the top of a source checkout.
It doesn't matter what directory you run from, as long as it's not at the top of a source checkout.


If you are running Debian or Ubuntu, you may be able to get it to work by:
If your hazards are all contained within js/src, you could use hazards/build_shell.py in place of hazards/build_browser.py. It will complete much more quickly.
 
If you are running Debian or Ubuntu, then there is currently a problem running the full browser analysis. You can coerce the shell-only build to work by doing something like:


   sudo apt-get install autoconf2.13 libnspr4 libnspr4-dev
   sudo apt-get install autoconf2.13 libnspr4 libnspr4-dev
Line 29: Line 30:


before running the script.
before running the script.
If your hazards are all contained within js/src, you could use hazards/build_shell.py in place of hazards/build_browser.py. It will complete much more quickly.


The easiest way to run an analysis is to push to try with the trychooser line |try: -b do -p linux64-br-haz| (or, if the hazards of interest are contained entirely within js/src, use |try: -b do -p linux64-sh-haz| for a much faster result). The expected turnaround time for linux64-br-haz is just under 2 hours. For b2g hazards, you can use -p linux64-b2g-haz.
The easiest way to run an analysis is to push to try with the trychooser line |try: -b do -p linux64-br-haz| (or, if the hazards of interest are contained entirely within js/src, use |try: -b do -p linux64-sh-haz| for a much faster result). The expected turnaround time for linux64-br-haz is just under 2 hours. For b2g hazards, you can use -p linux64-b2g-haz.
Confirmed users
329

edits

Navigation menu