Description:
The names of the test files for h5import changed slightly, so we needed to update our test script accordingly. Also, a test for EOL characters has been added.
Tested:
VS2005 on WinXP
Tools
-----
- h5import bug on Windows w/binary datasets. fread in windows needs a binary file
to be open with rb instead of r otherwise it terminates execution if an end
of file character is found on the input file. Besides that the binary file
generated needs to be open with wb , otherwise an end of line character is
read twice. PVN - 2008/2/19
renamed the h5import test files to have the extensions
text input files = .txt
binary input files = .bin
configuration files = .conf
hdf5 files = .h5
besides that in very test the files have the same name except extension.
For example
TOOLTEST txtin16.txt -c $srcdir/testfiles/txtin16.conf -o txtin16.h5
The convention for the test name is for example, for "txtin16"
"txt" for text then "in16" means integer 16 size
Tested: linux, solaris
Description:
List the new HL C examples that were added in the last checkin. Rather than listing each one individually, we give a brief summary, and instructions for how to test them.
Description:
The Windows suite of examples for HL C was a very small subset of the examples that exist for other platforms. Now we have all of the HL C examples-- integrated into the VS projects files, and batch test scripts.
Tested:
VS2005 on WinXP
VNET on WinXP
Description:
This is the same patch that Mike McGreevy helped me with on the 1.8 branch. The latest cygwin DLL has trouble with the global timezone variable. Now in configure, we target CYGWIN with a case statement, and avoid the problem.
Tested:
Cygwin on WinXP
Description:
The collection of HL C examples that we distribute for Windows is incomplete. I wasn't aware of it until Pedro pointed it out, because we use different (although similar) names for the generated files. This checkin changes the naming to follow Linux, in preparation to add the rest of the HL examples to Windows.
Note: I believe I've updated the MANIFEST accordingly, but I may have missed something-- I'll check on Linux shortly after this commit.
Tested:
VS2005 on WinXP
VS.NET on WinXP
Description:
For some reason, the hdf5_hl library didn't have hdf5 listed as a dependency. This isn't normally a problem, because building "all" will build hdf5 library. However, when a user tries to build only hdf5_hl, hdf5 library wouldn't be built.
Although not technically required for compiling the library code, the hdf5 library is needed for linking any applications, so it's a natural dependency.
Tested:
VS2005 on WinXP
VNET on WinXP
the H5Dset_extent function was done in 2002 but was at a time (2003-2006) previewed not to be used
it is now being used again
tested: windows, linux, solaris (in progress :-) )
Description:
Previously, all of our build output would simply go to stdout/stderr for command-line builds. We can pipe this into a log file as a whole, but the complete logfile becomes very large very quickly. Instead, we give the user an option to place build results and test results into separate logs (or even the same). This will help keeping track of results in our automated testing.
Tested:
VS2005 on WinXP
Fold all the updates made for v1.8.0 release to the main trunk.
Versions are from r14548 to r14556. Changes are,
Updated section 4 for v1.8 release.
(May still check the v1.6 INSTALL to see if something can be adopted from
there. But this is good for v1.8 release.)
Moved the section 2. "Warnings about compilers" to Appendix A; renumbered
section 3-7 to section 2-6 and fixed all section references.
Updated Website names from ncsa.uiuc.edu to hdfgroup.org or hdfgroup.uiuc.edu.
Updated section 1-3 and some of section 4.
Quick editorial review.
Convert tabs to spaces for consistent display and printing.
Verify and fix links and references.
Moved the following three paragraphs to the Appendix part since they have old
information that are not relevant most recent machines or compilers.
"Large (>2GB) versus small (<2GB) file capability",
"Building and testing with Intel compilers"
"Building and testing with PGI compilers"
Description:
We've run into a bug that was introduced in the latest version of Cygwin, that breaks C99 code using the 'timezone' global variable. As a workaround, we use the -ansi flag, which makes everything compile/link/test correctly
Tested: Cygwin on WinXP
Description:
Wrote documentation on how to use the 1.6 API for a user application-- this replaces the outdated documentation we previously had.
Tested: VS2005 with HDFEOS5
Description: IRIX64 failed to build tools/h5import, as well as c++/test
with szip. This is because IRIX is very picky when it comes
to linking libraries, and must be done in specific order.
(other UNIXes are not as such, and thus the problem wasn't
present).
Solution: Rearrange the order in which the libraries are
linked on the compiler line by sorting the line that
assigns libraries into the LDADD variable in the Makefile.am's
of the two respective directories.
Tested: IRIX64, kagiso, smirom
Description: config/lt_vers.am was updated as follows due to changes in API
since last version update:
LT_VERS_INTERFACE = 5
LT_VERS_REVISION = 0
LT_VERS_AGE = 0
Tested: kagiso
Description:
A user pointed out that one of our Fortran dependencies wasn't getting installed correctly due to a wrong path in our install file. After reviewing, I've applied the patch that he's proposed.
As best I can tell, H5C_make_space_in_cache() was accessing memory
that had been deallocated -- however the bug was easy to mask, and
jumped around even in different runs of the same executable. While
I was never able to generate a definitive test case that exposed
exactly where the core dump occured, I was able to generate print
statement traces which made it clear that I was accessing freed
memory.
In any case, reworking the code to avoid the reference to freed
cache entries seems to have fixed the problem.
Tested serial production on Phoenix, and commit tested. Also,
partial tests Linew.
detect and handle the case in which the skip list or LRU is modified
out from under a scan of same by the flush callback of the entry under
consideration.
Test serial debug, serial production, and parallel debug on phoenix,
and commit tested.
Description:
For some reason, the h5reparttst output folder wasn't set correcty for 64-bit Windows. This may have gotten accidentally changed with other intermediate project file changes.
Tested:
VS2005 on WinXP x64
callback functions modifies the skip list or LRU out from under a partial
or complete flush of the cache. This is a test for a situation that
should not occur, but we test anyway.
Also added code to skip longer tests in cache_api in express tests.
Tested serial and parallel on phoenix (debian --x86-32), and commit test.
Elena commit tested as well, and ran a manual test under MacOS X.
Description:
There was another update to the main h5dump test script. This checkin brings those edits to the Windows script as well.
Tested:
VS2005 w/ WinXP
large entry, or to a large increases in the size of an existing entry.
This required some additions to the cache configuration structure, and
thus will require changes in the metadata cache documentation.
The basic idea is to monitor the size of entries as they are loaded,
inserted, or increased in size. If the size of the entry (or increase)
exceeds some user selected fraction of the size of the cache, increase
the size of the cache.
Note that this fix was designed quickly -- while it deals with the
use case that exposed the problem, we may have to revisit the issue
later.
Tested serial and parallel on Phoenix, and h5committest.
