summaryrefslogtreecommitdiffstats
path: root/test/family_v16_00000.h5
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r16758] The test of family file compatibility with v1.6 used the ↵Raymond Lu2009-04-151-0/+0
| | | | | | | | | | original family files under the library source directory. Since the test opens the files with write mode, it's safer to make copies of the original files. I added the copying step in test_family_compat in vfd.c. I changed the Makefile.am to clean up the copied files. I created a new family_v16_00000.h5 with v1.6 library. Tested on jam - supposed to be simple change.
* [svn-r16740] Snapshot version 1.8 release 2 (post12)Larry Knox2009-04-121-0/+0
|
* [svn-r16733] Revert change to family_16_00000.h5 from latest snapshot ↵Neil Fortner2009-04-101-0/+0
| | | | | | release. Raymond is working on fixing this.
* [svn-r16725] Snapshot version 1.8 release 2 (post11)Larry Knox2009-04-101-0/+0
|
* [svn-r16608] Bug fix (#1161): When a family file created with v1.6 library ↵Raymond Lu2009-03-241-0/+0
| | | | | | | | | | | | is opened and closed with v1.8 library, v1.8 library writes the driver info block in the superblock. But v1.6 doesn't write it. This caused the data after the superblock to be overwritten. The solution is to use a flag to indicate when the original file doesn't have the driver info, v1.8 library doesn't write it either. Tested on jam. I have some trouble to access smirom and linew using h5committest.
* [svn-r14340] Maintenance for VMS system:Elena Pourmal2007-12-131-0/+0
Skip one of the tests in flush2.c since it looks like VMS system flsuhes the file anyway (like on Winodws with DLLs) Renamed files family*.h5 that are used in backward compatibility testing to have only one '.' in a file name, otherwise VMS system becomes confused and test fails. Cleaned up the only test (Fortran multi-file test) that is failing on VMS (C counterpart passesa). Added new script to facilitate the build process on VMS Updated MANIFEST PLatforms tested: VMS server, kagiso and linew (minor changes)