Javascript:Hazard Builds: Difference between revisions

Javascript:Hazard Builds (view source)

Revision as of 16:40, 29 July 2015

9 bytes removed , 29 July 2015

→‎Running the analysis: Updated instructions to something that'll actually work

Sfink

Confirmed users

328

edits

@@ Line 20: / Line 20: @@
 === Running the analysis ===
-Theoretically, you could run the analysis yourself by checking out mozharness and running
+To run the browser analysis, you must be on linux64 and do:
-   python mozharness/scripts/spidermonkey_build.py -c hazards/common.py -c hazards/build_browser.py -c users/sfink/spidermonkey.py
+   python testing/mozharness/scripts/spidermonkey_build.py -c developer_config.py -c hazards/common.py -c hazards/build_browser.py --source $SRCDIR
-but you'll need a bunch of dependencies that aren't bundled up in any convenient way, and you'll need to edit that last config file for your environment.
+Or if your hazards are all contained within js/src, you could use hazards/build_shell.py in place of hazards/build_browser.py.
-The far easier 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.
+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 output will be uploaded and a link will be placed into the build summary info pane on treeherder. If the analysis fails, you will see the number of failures (and the number of expected failures, which should usually be zero.)
+The output will be uploaded and a link named "results" will be placed into the "job details" info pane on treeherder. If the analysis fails, you will see the number of failures. Navigate to the hazards.txt.gz file.
 === Analysis output ===