Confirmed users
328
edits
Javascript:Hazard Builds: Difference between revisions
Jump to navigation
Jump to search
→Running the analysis: default directory would not work
(Only talk about hazard builds) |
(→Running the analysis: default directory would not work) |
||
| Line 14: | Line 14: | ||
To run the browser analysis, you must be on linux64 and do: | To run the browser analysis, you must be on linux64 and do: | ||
python testing/mozharness/scripts/spidermonkey_build.py -c developer_config.py -c hazards/common.py -c hazards/build_browser.py --source $SRCDIR | cd <gecko> | ||
mkdir work | |||
cd work | |||
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. | |||
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. | ||