First cut at script that converts start_test log to jUnit xml report.
python 2.6 arg parser
Open logs with utf-8 encoding. Ignore invalid characters.
Fix bug when finding blocks.

If end was not found (-1) it was still added to the start value, which gave a bad end value.
Support jUnit xml style reports in start_test.

Add --junit-xml argument. When set, start_test calls new script to convert
logfile to junit xml style report. Also add --junit-xml-file argument, which
implies the --junit-xml argument. When --junit-xml-file is set, its value is
passed along to the conversion script as the junit xml output file.
Add jUnit XML report generation support to nightly.

Add -junit-xml flag to nightly that add --junit-xml flag when calling
start_test. The flag is thrown by default when JENKINS_URL is set in
environment (i.e. nightly is running inside jenkins job).
Filter invalid XML characters and wrap system-out in CDATA tag.
Add DEBUG setting.
Fix bug that showed up in linux32 logs.
Merge branch 'master' of https://github.com/chapel-lang/chapel into junitxml-for-start-test
Add TODOs based on @Kyle-B's review.
Drop noperf tests, instead of skipping them.

When running performance tests, there are lots of tests that are skipped
because they do not have the performance configuration files. They should not
be included in the jUnit reports as they are not interesting data points. Real
performance tests that are skipped due to the environment/etc are still
included as skipped in the report.
Simplify third-party Makefiles.

This is a follow-up to https://github.com/chapel-lang/chapel/pull/1013,
which simplified third-party/gmp/Makefile{,.include}.  That passed
nightly testing last night, so now we're doing the other third-party
packages.

First, in Makefile.include (or for llvm, Makefile,share), change the
ordering of the make(1) variable definitions to be generally:

  base and unique build dirs
  build dirs
  install dirs
  source dirs and files, if any
  lib dirs and files, if any

Second, these lines in Makefile were superfluous:

  <pkg>_ABS_DIR = $(shell pwd)
  <pkg>_INSTALL_DIR = $(<pkg>_ABS_DIR)/$(<pkg>_INSTALL_SUBDIR)
  <pkg>_BUILD_DIR = $(<pkg>_ABS_DIR)/$(<pkg>_BUILD_SUBDIR)
  <pkg>_DIR = $(<pkg>_ABS_DIR)

Because <pkg>_ABS_DIR isn't referenced anywhere else, they're equivalent
to:

  <pkg>_DIR = $(shell pwd)
  <pkg>_INSTALL_DIR = $(<pkg>_DIR)/$(<pkg>_INSTALL_SUBDIR)
  <pkg>_BUILD_DIR = $(<pkg>_DIR)/$(<pkg>_BUILD_SUBDIR)

But these latter two definitions of <pkg>_{INSTALL,BUILD}_DIR are
identical to the ones in Makefile.include, which is included here by
virtue of ../../make/Makefile.base being included at the top. So they
can go. And the first definition here is effectively the same as this
one that is already in Makefile.include:

  <pkg>_DIR = $(shell pwd)/../../third-party/qthread

So, it can go as well.

While here, I also got rid of the unreferenced BINUTILS_GOLD_DIR
definition in the llvm Makefile, after checking with the author that
there was no expectation it would be needed in the future.
Fixed an issue in handleCaptureArgs()
Support suppressions when generating jUnit reports.
Remove todos.

Suppressions are now supported and multiple performance trials were already
being collected.
Pipe suppressions through start_test for jUnit reports.
Merge branch 'master' of https://github.com/chapel-lang/chapel into junitxml-for-start-test
Update future based on Brad's comments.
Adding one typeselect future and one test showing its pointless

twoTypeSelects.chpl shows that the current implementation of
type select does not support multiple type selects in a single
Chapel program.  D'oh!  It's probably a five-minute fix to get
this working if one cared to.  By the time I'd written up the
description in the .future, it seemed like I also had the
solution.  But...

deprecateTypeSlect.chpl shows the syntax I'd prefer to use for
"type select" statements and was intended as a feature request
future; but it turns out to work.  So it raises the question
"Do we even need a type select anymore?"  Until someone argues
convincingly otherwise, my answer is "no, it seems like we
don't."