| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
It failed when only 1 is used to test.
Solution:
Cleanup the code a little so that it works for any number
of processes to invoke it.
Platforms tested:
h5committested,
|
|
|
|
|
|
|
|
|
|
| |
Description:
Fixed typos and re-arranged some functions to be in sync with 1.6.
Platforms tested:
Linux 2.4 (heping)
SunOS 5.9 (shanti)
AIX 5.1 (copper)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: I am checking in changes for the h5stat tool:
- updated Makefile.am to use tools library
- regenerated Makefile.in
- added command flags to display selected information
- added support for external files and filters
- small output formatting changes
For more information about current features and output see
updated h5stat RFC http://hdf.ncsa.uiuc.edu/RFC/h5stat/h5stat-spec.pdf
Solution:
Platforms tested: mir, heping, shanti, copper 64-bit, copper 32-bit parallel
using files from tools/testfiles directory and some NASA files
from our Web site.
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some collective chunk IO macro names are confusing, change them to more meaningful
names.
Description:
H5Pset_dxpl_mpio_chunk_opt will set a flag so that the library can do one linked IO or mul
ti-chunk IO with collective in chunking storage directly. That is, the library won't do an
alyses to determine this.
The flags for the enum type we used before are:
H5FD_MPIO_OPT_ONE_IO
H5FD_MPIO_OPT_MULTI_IO
They are not good names because of the following two reasons:
1. It doesn't reflect chunking storage
2. OPT is kind of redundant and misleading,
Solution:
We change the names to
H5FD_MPIO_CHUNK_ONE_IO
H5FD_MPIO_CHUNK_MULTI_IO
Platforms tested:
Since only macro names are changed, no need to test with h5committest.
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some collective chunk IO macro names are confusing, change them to more meaningful
names.
Description:
H5Pset_dxpl_mpio_chunk_opt will set a flag so that the library can do one linked IO or multi-chunk IO with collective in chunking storage directly. That is, the library won't do analyses to determine this.
The flags for the enum type we used before are:
H5FD_MPIO_OPT_ONE_IO
H5FD_MPIO_OPT_MULTI_IO
They are not good names because of the following two reasons:
1. It doesn't reflect chunking storage
2. OPT is kind of redundant and misleading,
Solution:
We change the names to
H5FD_MPIO_CHUNK_ONE_IO
H5FD_MPIO_CHUNK_MULTI_IO
Platforms tested:
Since only macro names are changed, no need to test with h5committest.
heping(mpich 1.2.6)
Misc. update:
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Disable this file generator unless the group revision flag is enabled.
Platforms tested:
None, just eyeballed - very minor change
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
Sometimes the parallel prefix is given in the form of nfs:/mnt/pfs which
if given to a non-MPIO VFD like the default H5Fcreate, it would fail.
Called h5_rmprefix which would return the non-prefix component
part of the file name which would be okay for the default H5Fcreate and
such.
Platforms tested:
Tested in heping parallel.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Feature
Description:
Sometimes the parallel prefix is given in the form of nfs:/mnt/pfs which
if given to a non-MPIO VFD like the default H5Fcreate, it would fail.
Added a new routine h5_rmprefix which would return the non-prefix component
part of the file name which would be okay for the default H5Fcreate and
such.
Platforms tested:
Tested in heping parallel.
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Ran /bin/h5vers to change suffix to alpha4 after creating hdf5-1.8.0-alpha3
tar ball and tagging the release with hdf5_1_8_0_alpha3 tag
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Checking in files modifed by the bin/release script before
tagging hdf5-1.8.0-alpha3
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
| |
Misc. update: Document some errors in test/dt_arith.c when converting data from
long double to (unsigned) long long and from (unsigned) long long to long double.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Updated VMS installation instructions to reflect support
for the deflate filter; documented scale+offset test failures
when G_FLOAT is used (not IEEE double)
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
|
|
|
|
|
| |
Description: There was some logical confusion about the value of the macro
H5_HW_FP_TO_LLONG_NOT_WORKS. It's supposed to be true for Windows, but false
for Unix machines.
Solution: Corrected.
Platforms tested: fuss(Linux) and amazon(MacOS 10.4) - simple change.
|
|
|
|
|
|
|
|
|
|
| |
Description: dsets and objcopy tests were missing from the command files
Solution: Added appropriate commands to compile and run tests
Platforms tested: VMS server with native float
Misc. update:
|
|
|
|
|
|
|
|
|
| |
Description: Windows doesn't recognize "long long" but "long_long".
Solution: The library defined a more general type "long_long". Use
it instead.
Platforms tested: fuss - simple change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added Exress Test mode.
Description:
The test takes a long time to run. It tempted developers to skip the
h5committest.
Solution:
Added Express Test mode to allow tester an option to run it in express
mode (shorter time.) There are already encoded QAK macro which skips
many tests. Follow that pattern to skip tests when HDF5TestExpress is
set.
Platforms tested:
Tested in heping, both serial and parallel.
|
|
|
|
|
|
|
|
|
|
|
|
| |
feature.
Description:
Added the option of -64 which is similar to -n32. This is needed by
Atlantia which has the ABI as -n32.
Platforms tested:
Pretty straight forward but not testable by h5committest.
Will be tested when daily tests run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Feature
(Code and tests are done by Christian. I just committed the code.)
Description:
Rewrote the purpose of this test. Now it tests these three cases,
/*
* Test following possible scenarios,
* Case 1:
* Sequential create a file and dataset with H5D_ALLOC_TIME_EARLY and large
* size, no write, close, reopen in parallel, read to verify all return
* the fill value.
* Case 2:
* Sequential create a file and dataset with H5D_ALLOC_TIME_EARLY but small
* size, no write, close, reopen in parallel, extend to large size, then close,
* then reopen in parallel and read to verify all return the fill value.
* Case 3:
* Sequential create a file and dataset with H5D_ALLOC_TIME_EARLY and large
* size, write just a small part of the dataset (second to the last), close,
* then reopen in parallel, read to verify all return the fill value except
* those small portion that has been written. Without closing it, writes
* all parts of the dataset in a interleave pattern, close it, and reopen
* it, read to verify all data are as written.
*/
Platforms tested:
Tested in copper, tg-ncsa and heping, all in parallel mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
tg-login was having an error about H5match_types.Tpo being missing.
Solution:
tg-login was trying to build H5_match_types twice at the same time and
becoming confused as a result.
Massaged the dependencies in the Makefile.am to prevent this.
Platforms tested:
mir, sol, tg-login
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Added location of the zlib library compiled with /float=ieee_float
flag
Solution:
Platforms tested: VMS server
Misc. update:
|
|
|
|
|
|
|
|
|
|
| |
Description: Brought up VMS make files up to date
Solution:
Platforms tested: VMS server with native floating number and ZLIB enabled
Misc. update:
|
|
|
|
|
|
|
| |
Solution:
Misc. update: added hl/test/dtype_file_readable.txt
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Check in potential fix to unreproduceable bug in t_cache observed on
Cobalt
2) Check in code supporting added pinned entry features in the metadata
cache.
Description:
1) Elena encountered a bug in t_cache when running on Cobalt. On
investigation I found a potential race condition in t_cache that
could explain her observation.
2) Quincey requested additions to the metadata cache allowing renaming
of pinned entryies, and marking of pinned or protected entries as
dirty.
Solution:
1) Modified t_cache.c to prevent the potential race condition. Elena
was unable to reproduce the bug on Cobalt, so we don't know if my
fix actually addressed the problem.
2) Added code supporting the requested functions. The changes were
relatively trivial, but required substantial new test code.
Platforms tested:
h5committest, serial test on heping, parallel test on phoenix.
Misc. update:
|
|
|
|
|
|
|
|
|
| |
Description: dtype_file.txt is a text file for testing complicated compound type
for H5LTtext_to_dtype(). dtype_file_readable.txt is just a human-readable version
of dtype_file.txt for debugging purpose.
Platforms tested: No test.
|
|
|
|
|
|
|
|
|
|
|
| |
Makefile cleanup
Description:
Cleaned up where files were distcleaned
Platforms tested:
mir (change only affects distclean)
|
|
|
|
| |
Description: Copyright was missing from last commit.
|
|
|
|
|
|
|
|
|
|
| |
Description: The current code in Yacc parser doesn't handle big-endian
machine for enum type correctly.
Solution: Depending on the super type of enum, use appropriate integer
type to pass in enum value.
Platforms tested: h5committest and fuss.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
Shanti compiler destroy unnamed objects later than others, which caused
some reference counting test fail. Revised the test so that destructors
are called at the same time, regardless the differences of compiler
implementation.
Revised some constructors, close, operator=, and destructors to make
sure that all the object ids are handled properly.
Platforms tested:
Linux 2.4 (heping)
SunOS 5.9 (shanti)
HPUX 11.00 (kelgia)
AIX 5.1 (copper)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
Shanti compiler destroy unnamed objects later than others, which caused
some reference counting test fail. Revised the test so that destructors
are called at the same time, regardless the differences of compiler
implementation.
Revised some constructors, close, operator=, and destructors to make
sure that all the object ids are handled properly.
Platforms tested:
Linux 2.4 (heping)
SunOS 5.9 (shanti)
HPUX 11.00 (kelgia)
AIX 5.1 (copper)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fix.
Description:
More machines stop supporting "rsh machine command".
Worse yet, it hangs the "rsh machine command" process.
Solution:
Switch the order of testing remote execution to use
ssh first, then rsh.
Platforms tested:
no h5committest since it does not test this command.
Change is trivial and will monitor Daily test tonight.
|
|
|
|
|
|
|
|
|
|
|
| |
Code checkpoint
Description:
Add a few minor tweaks & corrections to the fractal heap code.
Platforms tested:
Linux 2.4 (chicago)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
| |
Portability fix
Description:
Try again to placate the VS 6.0 compiler
Platforms tested:
Linux 2.4 (chicago)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
When destroying the cache for a file, don't disconnect the cache from the
file structure until after the cache is shut dow, to allow pinned entries to
be unpinned.
Platforms tested:
Linux 2.4 (chicago)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code checkpoint
Description:
Update fractal heap code to allow objects to be deleted
Fix bugs in fractal heap object insertion
Improve free space manager code to allow sections to be merged and
shrink the container
Another try at making the Windows compilers happy...
Platforms tested:
FreeBSD 4.11 (sleipnir)
Mac OS X.4/PPC (amazon)
Linux 2.4 (chicago & heping)
Solaris 2.9 (shanti)
AIX 5.? (copper) w/parallel
|
|
|
|
|
|
|
|
| |
Document error.
Description:
The fix of the TR was put in the wrong session (new configure feature).
It is moved to the proper session (bug fix on configure.)
|
|
|
|
| |
Misc. update: added hl/test/dtype_file.txt.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
The ${TR}, though avoid the error, is inconvenient. It is needed
because configure.in use the char range in the style of 'a-z'.
The other style of '[a-z]' is more commonly accepted by all tr
but autoconf tends to strip away [], making the syntax rather
clumsy.
Solution:
Learned from autoconf that it avoids the use of character range
by just spell all the letters out. Changed our tr commands to
use those variables defined by autoconf. Also removed the
definition of ${TR} since it will cause inconsistancy when
autoconf also use plain 'tr' in its generated code.
The Makefile.in are changed because the elimination of ${TR} from
configure triggered its removal from all Makefil.in. That is okay
because ${TR} is not used at all in Makefile.
Platforms tested:
h5committested. (sol failed to connected). also tested in shanti
using both /usr/ucb/tr and /bin/tr (the bad one before.)
Misc. update:
Updated both INSTALL and RELEASE files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating project file
Description:
Due to the new added source codes under hdf5/src.
Solution:
Project file has to be changed to reflect this
Platforms tested:
VS 6.0 ( Failed during compiling because of compiler failure)
VS 7.0
Everything okay except that several h5repack tests get skipped.
Don't know whether this happens on other platforms.
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_none:S+O=31 -
SKIPED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -SKIP
ED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_scaleoffset:N
ONE -SKIPED-
h5repack -i test_all.h5 -o out.test_all.h5 -SKIP
ED-
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating project file
Description:
New source code has been added,
project files need to be updated.
Solution:
Platforms tested:
VS 6.0(build failed due to compiler problem)
VS 7.1(.Net 2003)
Everything okay except that several h5repack tests get skipped.
Don't know whether this happens on other platforms.
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_none:S+O=31 -
SKIPED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -SKIP
ED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_scaleoffset:N
ONE -SKIPED-
h5repack -i test_all.h5 -o out.test_all.h5 -SKIP
ED-
Misc. update:
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Avoid using double -> hsize_t conversion, to placate VS 6.0
Platforms tested:
None, just eyeballed...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
manifest update
Description:
one new file that was not updated yesterday
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
new function
Description:
added H5LTfind_attribute as a public function, a wrapper for the already existing private function
H5LT_find_attribute
Solution:
Platforms tested:
linux
solaris
Misc. update:
|
|
|
|
| |
Misc. update: Update this document for H5LTtext_to_dtype and H5LTdtype_to_text.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Yesterday, a definition of the macro YY_BUF_SIZE of 256KB
was committed in, but copper complained it can't be redefined.
Solution: Added #ifdef and #undef to make sure the macro is undefined
first. Also integrated a complicated compound type test. It reads
input from a text file. The datatype is unusually large, of 101 member
fields.
Platforms tested: h5committest and fuss.
|
|
|
|
|
|
|
|
|
|
| |
Description: The default size for input buffer of Lex is only 8K. Some
application has input string far bigger than it.
Solution: Increase the size by defining YY_BUFFER_SIZE to be 256K (262144)
in H5LTanalyze.l
Platforms tested: fuss - simple change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code checkpoint
Description:
Checkpoint fractal heap improvements, as well as move the free space
manager code that it's using into a separate package.
Platforms tested:
FreeBSD 4.11 (sleipnir)
Linux 2.4/64 (mir) w/C++ & FORTRAN
Linux 2.4/32 (heping)
Solaris 2.9 (shanti)
AIX 5.? (copper) w/FORTRAN & parallel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
Some machines (e.g., HPUX) will have off64_t defined but no support
for stat64 unless certain LargeFile macro is turned on. This caused
the last fix on H5private not quite right which caused compiling failures.
Solution:
Added stat64 and fstat64 tests and then will use them only if they
are supported.
Platforms tested:
Tested on kelgia, copper and heping (pll).
(Compiling alright but tests for kelgia and heping are not done.
expect no problems.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: When --enable-group-revision flag was used, h5fget_filesize_f
function returned different value from expected one. Test failed
with false negative result.
Solution: Added Fortran function h5_group_revision_f and its
C stub to check if macro H5_GROUP_REVISION is defined.
Expected value from h5fget_filesize_f is set up accordingly.
Platforms tested: copper, shanti and heping with and without
--enable-group-revision configuration flag
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Added support for Zlib compression on VMS
Solution: Modified command files to add compilation and linking with
the ZLIB library.
Platforms tested: VMS servere with the VAX floating datatype;
will test IEEE option later
Misc. update:
|
|
|
|
|
|
|
|
|
|
| |
Description: Function prototype H5E_walk_t and structure H5E_error_t wasn't backward
compatible.
Solution: Make them compatible with v1.6 and provide new definitions of H5E_walk_stack_t
and H5E_error_stack_t.
Platforms tested: fuss and h5committest.
|