diff options
author | John Mainzer <mainzer@hdfgroup.org> | 2010-11-19 19:11:30 (GMT) |
---|---|---|
committer | John Mainzer <mainzer@hdfgroup.org> | 2010-11-19 19:11:30 (GMT) |
commit | 2f5d9e1c8a3ff11dc41394bc41d8634698c1e799 (patch) | |
tree | 7d26e16b7f2a130fd20c6ea5d0194f6ae3f82e40 /CMakeLists.txt | |
parent | 4bc498cbe118d19e54d1064d4cd9f23c0ab8b94a (diff) | |
download | hdf5-2f5d9e1c8a3ff11dc41394bc41d8634698c1e799.zip hdf5-2f5d9e1c8a3ff11dc41394bc41d8634698c1e799.tar.gz hdf5-2f5d9e1c8a3ff11dc41394bc41d8634698c1e799.tar.bz2 |
[svn-r19831]
Checked in fix for failure in shape same tests that appeared after
Quincy's recent massage of the test code. The problem was a race
condition created when Quincey re-worked the code selecting either
collective or independant I/O.
Previously, when independant I/O was selected in the test, I had
used H5Pset_dxpl_mpio() and H5Pset_dxpl_mpio_collective_opt() to
select collective semantics with independant I/O going on under
the hood. Quincey modified this to call H5Pset_dxpl_mpio() when
collective I/O was selected, and do nothing in the independant I/O
case. As a result, processes were able to race ahead and
modify the initial values of the data set before some processes
had verified that the initialization was correct.
Solved the problem by adding barriers, and making all barriers
dependant on independant I/O being selected.
Tested parallel on amani and phoenix. h5committested.
Diffstat (limited to 'CMakeLists.txt')
0 files changed, 0 insertions, 0 deletions