diff options
author | lrknox <lrknox> | 2017-03-15 17:49:19 (GMT) |
---|---|---|
committer | lrknox <lrknox> | 2017-03-15 17:49:19 (GMT) |
commit | 98567db19290dc07cc86efae720b0dc457ae9f65 (patch) | |
tree | 6b16f1d271bbc6c7a336d882c0e0db0f404dd3dc /test/vds_swmr_gen.c | |
parent | bf69edf565e4894b01afbd1efdedbc38eb18114a (diff) | |
download | hdf5-98567db19290dc07cc86efae720b0dc457ae9f65.zip hdf5-98567db19290dc07cc86efae720b0dc457ae9f65.tar.gz hdf5-98567db19290dc07cc86efae720b0dc457ae9f65.tar.bz2 |
output_filter.sh:
Comment added to address HDFFV-8270. The sample ontput in the
file's comments are not up-to-date with the scripts in the file
that remove output unique to certain systems when running test
scripts. This output doesn't match expected output files for
the tests, causing them to fail. Ther output_filter.sh file
removes such output. Currently we don't have access to these
systems to update the comments.
testflushrefresh.sh.in:
flushrefresh and other SWMR tests have been failing
occasionally but regularly since bringing them to the develop
branch. The logs and debugging point to unexpected deletion of
signal files as the point of failure, and John Mainzer suggests
that two such tests running simultaneously in the same directory
may lead to the operating system deleting the other test's
signal file. Running the flushrefresh test in its own directory
seems to solve the problem.
Diffstat (limited to 'test/vds_swmr_gen.c')
0 files changed, 0 insertions, 0 deletions