Added a .skipif and removed a .notest on directories.
Merge pull request #1040 from vasslitvinov/adjust-skipif-notest-on-some-dirs

Added a .skipif and removed a .notest on directories.

* Removed this:

    test/studies/cholesky/jglewis/cholesky_subs.notest

because our test scripts currently do not honor the files
"<dirname>.notest", and that directory has a NOTEST.

* Added this, with a trivially-true condition, to skip testing it:

    test/studies/lulesh/release-valgrind/orig-dir.skipif

Explanation:

'orig-dir' is a symlink to the directory that's tested anyway:

    release/examples/benchmarks/lulesh

paratest.server descends into that directory *additionally*
as a child of studies/lulesh/release-valgrind. [1]
This is unnecessary *and* can cause spurious failures. [2]
The .skipif avoids this.

[1] Q: Why does paratest.server descend into it?

A: paratest.server tests whether it is a directory using
    if (-d "$targetdir/$filen")
paratest.server being written in perl, that returns 'yes',
so that directory goes on the list of all directories
to pass to paratest.client.

Q: Why does start_test NOT descend into it?

A: start_test finds the list of directories using "find -type d".
A symbolic link does not satisfy this -type d for 'find',
so that path does not end up on the to-test list.

[2] This is because paratest.server can unwittingly make two
paratest.clients test release/examples/benchmarks/lulesh,
once as itself and once as studies/lulesh/release-valgrind/orig-dir

In general, when the same directory is tested by two start_tests
in parallel, spurious failures are easy to come by.

In this case, one process (OP) creates coords.out while the second process
(SP) has already deleted it and relies on not having it.
SP's .good expects "cat: coords.out: No such file or directory"
which fails because OP just created it.