Confirmed users
329
edits
Javascript:Automation Builds: Difference between revisions
Jump to navigation
Jump to search
m
headers
(tsan info) |
m (headers) |
||
| Line 32: | Line 32: | ||
* SM(tsan) - tsan | * SM(tsan) - tsan | ||
= Specific Build Information = | |||
== SM(pkg) == | |||
The SM(pkg) builds create a tarball of all the sources used to make a standalone SpiderMonkey library and shell, untar it somewhere else, and then runs the autospider command listed above. To reproduce this packaging and unpackaging behavior, you can run this command: | The SM(pkg) builds create a tarball of all the sources used to make a standalone SpiderMonkey library and shell, untar it somewhere else, and then runs the autospider command listed above. To reproduce this packaging and unpackaging behavior, you can run this command: | ||
| Line 40: | Line 40: | ||
<gecko-root>/testing/taskcluster/scripts/builder/build-sm-package.sh | <gecko-root>/testing/taskcluster/scripts/builder/build-sm-package.sh | ||
== SM(tsan) == | |||
sm-tsan is a dynamic thread safety checker, which means that any given run will only report a subset of issues. Also, we have a number of errors currently in the codebase that it will allow through without turning the build red. These are listed in | sm-tsan is a dynamic thread safety checker, which means that any given run will only report a subset of issues. Also, we have a number of errors currently in the codebase that it will allow through without turning the build red. These are listed in | ||