mirror of
https://github.com/HDFGroup/hdf5.git
synced 2025-01-30 15:32:37 +08:00
2933d2f80b
The failure was caused by some over active sanity checking code in unlock_entry(). In essence the code did not consider the possibility that under certain, very unusual circumstances, an entry could be flushed to disk during the H5AC_unprotect() call. Instead, it simply failed if a dirty entry was marked clean after the call to H5AC_unprotect(). This bug in the test code was exposed by recent changes to the default cache configuration made as part of the "metadata blizard" bug fix. Fixed the bug by adding code to detect when an entry is flushed during the call to H5AC_unprotect(), and not trigger a failure if a dirty entry is marked clean after a call to H5AC_unprotect() if the entry has been flushed. In passing also found and fixed another test bug in which expunged entries were erroneously marked as dirty in the test code's independant register of entry status. Tested parallel on Phoenix (AMD64 Linux) and Jam. Also ran t_cache manually hundreds of times looking for intermittant failures. Larry kindly tested (parallel) on Mercury. |
||
|---|---|---|
| bin | ||
| c++ | ||
| config | ||
| examples | ||
| fortran | ||
| hl | ||
| perform | ||
| release_docs | ||
| src | ||
| test | ||
| testpar | ||
| tools | ||
| vms | ||
| windows | ||
| windows_vnet | ||
| .autom4te.cfg | ||
| .h5chkright.ini | ||
| aclocal.m4 | ||
| acsite.m4 | ||
| configure | ||
| configure.in | ||
| COPYING | ||
| Makefile.am | ||
| Makefile.dist | ||
| Makefile.in | ||
| MANIFEST | ||
| README.txt | ||
HDF5 version 1.9.30 currently under development
==> README.txt <==
Messages to be sent to the list should be sent to "<list>@hdfgroup.org".
Periodic code snapshots are provided at the following URL:
ftp://ftp.hdfgroup.uiuc.edu/pub/outgoing/hdf5/snapshots
Please read the README.txt file in that directory before working with a library
snapshot.
The HDF5 website is located at http://hdfgroup.org/HDF5/
Bugs should be reported to help@hdfgroup.org.