Javascript:Automation Builds: Difference between revisions

Javascript:Automation Builds (view source)

Revision as of 01:13, 20 May 2017

1,198 bytes added , 20 May 2017

tsan info

Sfink

Confirmed users

328

edits

@@ Line 32: / Line 32: @@
 * SM(tsan) - tsan
-== Aside on SM(pkg) ==
+== Specific Builds ==
+=== 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:
    <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
+  <gecko-root>/js/src/devtools/automation/variants/tsan
+under the 'expect-errors' key. These are a list of filename,function pairs. (We cannot use a line number because it would change whenever lines are added/removed.) For a given build, errors are summarized in a tsan_summary.txt artifact, and the detailed stack information produced by tsan will be bundled up in a tsan.tar.gz file containing per-pid outputs.
+The mrgiggles server is running a script that downloads and categorizes the observed failures, but it isn't done yet (it misses some pushes), and it does not yet expose the information it collects. If you're looking into a specific failure, you can either dig it out of tsan.tar.gz, or ask sfink for the detailed failure information. (mrgiggles watches for job completions, downloads tsan.tar.gz, and records the failure stacks in a file named after the filename, line number, and function name.)