Remove the global summary filename and file pointer; pass them in to the
summary functions as needed.  Error check the results of buffered I/O
calls.

(cherry picked from commit b67a93ff)

Introduce a CLAR_XML option, to run the `ctest` commands with the new
`-r` flag to clar.  Permitted values are `OFF`, `ON` and a directory to
write the XML test results to.

(cherry picked from commit a2d73f56)

Accept an (optional) value for the summary filename.  Continues to
default to summary.xml.

(cherry picked from commit baa5c20d)

(cherry picked from commit dbebcb04)

(cherry picked from commit 59f1e477)

(cherry picked from commit 3a9b9631)

This makes it possible to keep track of every test status (even
successful ones), and their errors, if any.

(cherry picked from commit bf9fc126)

Previously, supplying `-s` to explicitly enable some test(s) would run
the tests immediately from the argument parser.  This forces us to set
up the entire clar environment (for example: sandboxing) before argument
parsing takes place.

Refactor the behavior of `-s` to add the explicitly chosen tests to a
list that is executed later.  This untangles the argument parsing from
the setup lifecycle, allowing us to use the arguments to perform the
setup.

(cherry picked from commit 90753a96)

(cherry picked from commit 76cfeb20)

(cherry picked from commit 6fc946e8)

(cherry picked from commit 7238a1e8)

(cherry picked from commit 40c3a974)

Otherwise you get something like

Emitted 525 C/C++ compilation units (100%) successfully

525 C/C++ compilation units (100%) are ready for analysis
The cov-build utility completed successfully.
Build successfully submitted.
Received error code 200 from Coverity

travis_time:end:14cf6373:start=1534254309066933889,finish=1534254728190974302,duration=419124040413
The command "if [ -n "$COVERITY" ]; then ../ci/coverity.sh; fi" exited with 1.
travis_time:start:01ed61d4
$ if [ -z "$COVERITY" ]; then ../ci/build.sh && ../ci/test.sh; fi

travis_time:end:01ed61d4:start=1534254728197560961,finish=1534254728202711214,duration=5150253
The command "if [ -z "$COVERITY" ]; then ../ci/build.sh && ../ci/test.sh; fi" exited with 0.

Done. Your build exited with 1.

(cherry picked from commit 351ca661)

(cherry picked from commit 658b8e8a)

(cherry picked from commit 3ce31df3)

(cherry picked from commit a1ae41b8)

The new Travis cron job gets executed daily, but our current
configuration will cause each job to execute our Coverity script instead
of the default build and testing scripts. This cannot work, as Coverity
is heavily rate-limiting its API, so our cron builds are doomed to
always fail. What we want to do instead is execute our normal builds,
but add an additional Coverity jobs.

This can easily be done by adding another Coverity-specific job with a
conditional "type = cron", which sets the "COVERITY" environment
variable. Instead of checking the build type, we then simply check
whether "COVERITY" is set or not.

(cherry picked from commit 0a6c13a2)

(cherry picked from commit cd788314)

Homebrew's formula for openssl is "keg-only", which means it does not
install it into /usr/local.  On macOS builds, we need to set
PKG_CONFIG_PATH to include it.

(cherry picked from commit abf53363)

(cherry picked from commit d076db11)

Instead of trying to run coverity builds during the regular PR process,
run them during a regularly scheduled cron process.  These only need to
run nightly, so it makes sense to bring them out of the PR process.

(cherry picked from commit 6b92368c)

(cherry picked from commit 24d17562)

(cherry picked from commit 24b8dd82)

(cherry picked from commit 465f8b51)

(cherry picked from commit f7bb4ff8)

(cherry picked from commit 6fb63c92)

(cherry picked from commit dc6e80e2)

The leaks process is not good about handling children.  Ensure that its
child is `nohup`ed so that the grandparent shell won't wait for it to
exit.

(cherry picked from commit 6eb97b6b)

(cherry picked from commit 230eeda8)

(cherry picked from commit b00672b9)

(cherry picked from commit afecd15c)

(cherry picked from commit 7f12c123)

On Linux (where we run valgrind) allocate a smaller buffer, but still an
insanely large size.  This will cause malloc to fail but will not cause
valgrind to report a likely error with a negative-sized malloc.

Keep the original buffer size on non-Linux platforms: this is
well-tested on them and changing it may be problematic.  On macOS, for
example, using the new size causes `malloc` to print a warning to
stderr.

(cherry picked from commit 219512e7)

(cherry picked from commit 6d6700d2)

(cherry picked from commit 67f5304f)

(cherry picked from commit 9e588060)

Script to set up dependencies on a macOS build system.

(cherry picked from commit 87342404)

Sets up a linux host to prepare for a build.

(cherry picked from commit 5bb2087b)

Refactor citest.sh to enable local testing by developers.

(cherry picked from commit 451b0017)

(cherry picked from commit bf418f09)