Confirmed users
328
edits
Javascript:Hazard Builds: Difference between revisions
m
→Static Rooting Analysis: update to new biulds, TH
(updated to current reality) |
m (→Static Rooting Analysis: update to new biulds, TH) |
||
| Line 9: | Line 9: | ||
== Static Rooting Analysis == | == Static Rooting Analysis == | ||
Treeherder can run three static analysis builds: the full browser (linux64-br-haz), B2G (linux64-b2g-haz), and just the JS shell (linux64-sh-haz). They show up on treeherder as '''H''' (or '''SM(H)'''). | |||
These builds are performed as follows: | These builds are performed as follows: | ||
| Line 26: | Line 26: | ||
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. | 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. | ||
The far easier way to run an analysis is to push to try with the trychooser line |try: -b do -p linux64-br-haz | 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 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 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.) | ||