Open Bug 1308401 Opened 6 years ago Updated 6 years ago
Make sure scan-build doesn't fail silently
scan-build tests may not actually do anything if the script isn't correct. After messing up run_scan_build.sh recently we got this > nss/automation/taskcluster/scripts/run_scan_build.sh: line 43: [: 0: unary operator expected but a green scan-build on treeherder. This shouldn't happen.
That's because commands that fail on a pipeline or on conditionals (if, while) don't trigger `set -e` aborts.
You need to log in before you can comment on or make changes to this bug.