[Chapel Merge] Avoid using catfiles for lulesh testing

Branch: refs/heads/master
Revision: 5e72aa5
Author: ronawho
Log Message:

Merge pull request #17086 from ronawho/no-lulesh-catfiles

Avoid using catfiles for lulesh testing

[reviewed by @bradcray]

Add an option to lulesh to print coords to stdout instead of a file and
use that for correctness testing. Some launchers and systems do not
guarantee that files written by a job will be visible on disk by the
time the job completes. This was causing issues for lulesh where it
writes output to coords.dat and we then try to cat the file to our
output, but the file wasn’t visible on disk when we tried to cat.

We have seen this in the past on systems using pure aprun (no qsub) and
recently on systems using lsf/bsub.

Modified Files:
R test/release/examples/benchmarks/lulesh/PRECOMP
R test/release/examples/benchmarks/lulesh/lulesh.catfiles
R test/release/examples/benchmarks/lulesh/lulesh.cleanfiles
R test/release/examples/benchmarks/lulesh/test3DLulesh.catfiles
R test/release/examples/benchmarks/lulesh/test3DLulesh.cleanfiles
M test/release/examples/benchmarks/lulesh/lulesh-noargs.good
M test/release/examples/benchmarks/lulesh/lulesh.chpl
M test/release/examples/benchmarks/lulesh/lulesh.execopts
M test/release/examples/benchmarks/lulesh/test3DLulesh.execopts
M test/release/examples/benchmarks/lulesh/test3DLulesh.good

Compare: Comparing 8feb8dc51614...5e72aa52f8f7 · chapel-lang/chapel · GitHub