Fixed a minor glitch in each of sub_test and paratest.server
Followed up on Tom's reviewer comments.
Merge pull request #616 from vasslitvinov/minor-sub_test-paratest-fixes

Fixed a minor glitch in each of sub_test and paratest.server

* In sub_test, eliminate the confusion between $CHPL_HOME/test/users/USERNAME/... and /users/USERNAME.

I suspect that the conditional that I eliminated was added so you can say "start test somedir/sometest.chpl" and have it test $CHPL_HOME/test/somedir/sometest.chpl even when you are not in $CHPL_HOME/test. If so, sub_test does not implement this consistently. I.e. for a few sometest.* files, PREDIFF, etc., sub_test looks them up in the current directory always. So I force the other files to be looked up in the current directory, too.

* For "paratest.server --show-all-errors", show each error just once. While there, streamlined the code.

Reviewed by Tom.
Fix up a couple of comments in start_test
Merge pull request #681 from vasslitvinov/fixup-comments-in-start_test

Fixed up a couple of comments in start_test
that are related to $CHPL_TEST_PERF_DIR

One comment was technically incorrect.
For the other one I just fixed the phrasing.

Trivial, not reviewed.
Removing inline-oriented suppressions from baseline.suppress

For some time now, we've thrown --inline when doing --baseline
testing for reasons that I can't quite recall.  This has caused
tests that used to be suppressed for baseline testing (because
they test that inlining is working) to result in errors because
the expected suppression wasn't found.

This commit comments out those suppressions and adds an
explanation such that, if/when we make --baseline testing
just throw --baseline again, the history is visible in the
file.
Merge pull request #683 from bradcray/fix-baseline-suppressions

Removing inline-oriented suppressions from baseline.suppress

For some time now, we've thrown --inline when doing --baseline
testing for reasons that I can't quite recall. This has caused
tests that used to be suppressed for baseline testing (because
they test that inlining is working) to result in errors because
the expected suppression wasn't found.

This commit comments out those suppressions and adds an
explanation such that, if/when we make --baseline testing
just throw --baseline again, the history is visible in the
file.
Add some advice for how to clean up your master branch of erroneous commits that
have not been pushed to your remote fork.
Strip leading whitespace to make refArgIsWide match on darwin
Update based on Kyle's comments
Merge pull request #684 from lydia-duncan/addGitAdvice

Git master branch fix advice [reviewed by Kyle]

Add some advice for how to clean up your master branch of erroneous commits
that have not been pushed to your remote fork.
Parallel addition of indices while element accesses occur simultaneously is unsafe in our implementation of DefaultAssoaciative.
This is because a resize will invalidate references to elements previously accessed.
This test cannot be made to fail deterministically, so instead of becoming a future
it will be removed.
Merge pull request #687 from benharsh/parsafe-add-fix

Remove parSafeAdd as a test
Merge pull request #685 from Kyle-B/kb-fix-darwin-refArgIsWide

Strip leading whitespace to make refArgIsWide match on darwin

`wc -l` has leading whitespace on OSX, everything matches once it is removed.