| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
The table of error messages was updated in H5E.c. The change wasn't
reflected in this test because, sadly, we use hardcoded numerical
values for the "error" we want to check for and not the symbols.
Solution:
Bumped up the error number from 32 to 34 to coincide with the error
we expect.
Platforms tested:
Linux
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
when a snaptest did not complete, it reported it as a failure
of the launching host, rather than the testing host.
Changed it to report the testing host.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
On some SGI machines (or, rather, it was showing up there), the
/usr/ncsa/lib directory was being placed before the other directories
in the linker line. This was causing the linker to link in
alternative HDF5 libraries than the test library.
Solution:
Modified my previous hack so that it puts the $rpath macro at the
end, since those are the ones we're passing into the libtool function
(in the DYNAMIC_DIRS macro).
Platforms tested:
Paz
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Updated
Description:
Wrote description of fixes to the h5dumper vis-a-vis the -v and -i
options.
Platforms tested:
Stone Tablets.
|
|
|
|
|
|
| |
Improved format of failures reporting.
Platforms tested:
eirene, premium, modi4.
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Feature Addition
Description:
Added support for gcc 3.0.x. GCC 3.0.x supports the C99
specification. The "-std=c99" gets rid of those annoying "warning
long long not supported by ANSI standard" messages.
Platforms tested:
Linux and gcc 3.0.1
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
Was getting warnings about converting pointers to integers
without a cast.
Solution:
Changed some of the RETURN ERRORs from returning NULL to
returning FAIL instead.
Platforms tested:
Linux
|
|
|
|
|
|
|
|
| |
Tweaks
Description:
Improved the readability of the output and added some time information.
Platforms tested:
Solaris 2.6 (baldric)
|
|
|
|
|
|
|
|
|
| |
Feature
Description:
Changed some output format.
Improved the CHECK_RSH to better report the result when failed.
Platforms tested:
eirene with nosuch and shalom. (made sure failures do occur)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
Object IDs command-line options weren't being picked up.
Solution:
The wrong flag was being checked for. Changed the flag from "v" to
"i", which is what the documentation says.
Platforms tested:
Linux
|
|
|
|
| |
slight change of output format.
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup
Description:
This was "thrown" together in a quick way to test MPIO functionality.
Cleaned out some embrassingly useless declaration to reduce compiler
warnings.
Platforms tested:
modi4-pp and eirene-pp.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
SAF test code exposed an error in the HDF5_MPI_OPT_TYPES
code. The SAF code was doing collective write to chunked
storage dataset. Some processes wanted to flush some chunk
while some other processes were doing something else but the
HDF5_MPI_OPT_TYPES code thought the chunk flushing were collective
calls since it only looked at the condition when H5Dwrite
was called. So, it hanged when doing MPI_File_setview.
For now, turned off the HDF5_MPI_OPT_TYPES code so that the
SAF code would work. More long term fix later.
Platforms tested:
modi4(pp)
|
|
|
|
|
|
|
|
|
|
|
| |
bug fix
Description:
H5FD_mpio_flush() would try to file seek negative if the
file->eoa is 0 (e.g., doing mpio on the raw-file of the
split file driver). Put in a code to catch this case
by returning succeed immediately.
Platforms tested:
modi4(pp)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
When the Fortran interface was used on the Linux systems, there were segmentation
errors. This was caused because two arrays were being accessed outside of their
bounds and because the trace type parameters were specified inccorectly in
the ProcTrace.inc file. There were also problems on some systems caused because
the long names of HDF entries resulted in trace IDs which were too long.
Solution:
The lines where arrays were being accessed outside of their bounds were changed.
The code in the Makefile.in and the PabloSedscr sed script file were changed so
that the tracetype parameters were generated correctly. The PabloSedscr file was
also modified to eliminate trace IDs for individual entries.
Platforms tested:
LINUX, IRIX64, IBM SP2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Byte swapping routine was core dumping when attempting to convert 0
elements.
Solution:
Don't try to byte swap when there is nothing to do... :-)
Apologies to Kent for my comments on Friday about testing his checkins,
especially when it was I who needed to do moer testing. :-/
Platforms tested:
Solaris 2.7 (arabica)
|
|
|
|
|
|
|
|
|
|
| |
Bug fix.
Description:
Byte swapping algorithm wasn't converting the last 8 elements correctly.
Solution:
Used correct variable... :-)
Platforms tested:
FreeBSD 4.4 (hawkwind)
|
|
|
|
|
|
|
| |
Purpose:
Update
Description:
Added new test files
|
|
|
|
|
|
|
|
|
|
|
| |
Code improvement
Description:
The byte swapping routine for data conversion was inefficient.
Solution:
Applied a number of optimizations which should yield around a 2-3 times
faster algorithm.
Platforms tested:
Solaris 2.6 (baldric)
|
|
|
|
|
|
|
|
|
| |
Purpose:
add another raster image 24-bit test files
Description:
Solution:
Platforms tested:
sol 2.7 and RedHat Zoot 6.2
|
|
|
|
|
|
|
|
|
| |
Purpose:
update the expected HDF5 files to follow the interlace mode convention
in HDF5 image spec.
Description:
Solution:
Platforms tested:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
add another test file
Description:
Solution:
Platforms tested:
eirene, arabica
[machines you have tested the changed version. This is absolute
important. Test it out on at least two or three different platforms
such as Big-endian-32bit (SUN/IRIX), little-endian-32(LINUX) and
64-bit (IRIX64/UNICOS/DEC-ALPHA) would be good.]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Add another test file
Description:
Solution:
Platforms tested:
eirene, arabica
[machines you have tested the changed version. This is absolute
important. Test it out on at least two or three different platforms
such as Big-endian-32bit (SUN/IRIX), little-endian-32(LINUX) and
64-bit (IRIX64/UNICOS/DEC-ALPHA) would be good.]
|
|
|
|
|
|
|
| |
Purpose:
add another test case.
Description:
Solution:
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
a bug fix
Description:
change PIXEL_INTERLACE to INTERLACE_PIXEL and other interlace mode description
to fit for the image specification.
Solution:
Platforms tested:
eirene, sol2.7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
1. fix a bug
2. turn off a feature
Description:
1. change the output of GRgetiminfo from NULL to &interlace_mode.
2. turn off the feature to change line-interleaved feature into
pixel-interleaved feature since inconsistent behaviour is found
in GR interface.
Solution:
see above
Platforms tested:
eirene, arabica
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
add a real raster-24 bit testing for interlace mode.
Description:
1. GR interfaces will never create an HDF4 file with interlace mode other than
pixel interleaved. DF24 interfaces can create HDF4 file with different interleaved.
There are inconsistent behaviors between GRreqimageil and GRreadimage, data read into the memory will not behave properly if a new interlace mode is asked.
2. Currently HDF5 image spec. supports pixel interleaved and plane interleaved.
We make a real image file to test whether the converter is doing the right thing.
Solution:
We use DF24 bit APIs to generate a real image file that can be tested by H5view.
Platforms tested:
linux and sol2.7
|
|
|
|
|
|
| |
updated
Platforms tested:
bin/chkmanifest
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup
Description:
Changed prototype for the buffer in Attribute::write from "void *"
to "const void *"
Platforms tested:
FreeBSD 4.4 (hawkwind)
SunOS 5.7 (arabica)
Linux 6.2 (eirene)
|
|
|
|
|
|
|
|
| |
cleanup
Description:
chunk, iopipe, overhead have been moved to perform/.
Platforms tested:
eirene(parallel).
|
|
|
|
|
|
|
|
| |
cleanup
Description:
mpi-perf and perf have been moved to perform/.
Platforms tested:
eirene(pp)
|
|
|
|
|
|
|
|
| |
cleanup
Description:
perf.c and mpi-perf.c have been moved to perform/.
Platforms tested:
eirene (parallel)
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug fix
Description:
Could not get to compile as parallel program in parallel mode.
That was because I did not include hdf5.h before testing for the
H5_HAVE_PARALLEL macro. (DUMB!)
Solution:
#include hdf5.h first.
Platforms tested:
eirene (parallel)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup (sorta)
Description:
When the first versions of the HDF5 library were designed, I remembered
vividly the difficulties of porting code from a 32-bit platform to a 16-bit
platform and asked that people use intn & uintn instead of int & unsigned
int, respectively. However, in hindsight, this was overkill and
unnecessary since we weren't going to be porting the HDF5 library to
16-bit architectures.
Currently, the extra uintn & intn typedefs are causing problems for users
who'd like to include both the HDF5 and HDF4 header files in one source
module (like Kent's h4toh5 library).
Solution:
Changed the uintn & intn's to unsigned and int's respectively.
Platforms tested:
FreeBSD 4.4 (hawkwind)
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Included all those generated temporary files in the CLEAN target
so that they would be cleaned in "make clean".
Platforms tested:
eirene.
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Moved the position of the target of perform so that it is
included in compiling but not in the 'check' target.
Platforms tested:
eirene.
|
|
|
|
|
|
|
|
|
|
| |
Bug fix/code cleanup
Description:
Was using old-style property list for dataset transfer.
Solution:
Switched to use generic property list code for dataset transfer proplist.
Platforms tested:
FreeBSD 4.4 (hawkwind)
|
|
|
|
| |
Update dependencies, etc.
|
|
|
|
| |
Update manifest..
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Add missing dependency file.
Platforms tested:
FreeBSD 4.4 (hawkwind)
|
|
|
|
|
|
|
|
|
| |
new feature
Description:
Added perform programs to test the HDF5 library performance. Programs
are installed in directory perform/.
Platforms tested:
eirene
|
|
|
|
|
|
|
|
|
| |
New feature
Description:
Added perform programs to test the HDF5 library performance. Programs
are installed in directory perform/.
Platforms tested:
eirene
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New feature
Description:
Started this directory for performance measurement programs.
The programs here got compiled but not automatically run (just
like the examples direcotry.)
The programs have existed but now gathered to this one directory.
iopipe.c, chunk.c and overhead.c were from test. perf.c and mpi-perf.c
were from testpar.
Platforms tested:
eirene (serial and parallel).
overhead failed during run due to some property error. This is probably
due to the recent change of properties code.
perf and mpi-perf do not compile correctly for Parallel mode.
Checking them to make them available to others.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Improvement
Description:
The stdout and stderr were both redirected to an output file. This
works fine in tradition sequential Unix machines. But in some
parallel systems (like mpi-jobs in IBM SP), the stderr is merged
with stdout alright but not in the exact order as expected. This
is not deterministic in parallel jobs. So, the test output are
all there but the ordering maynot be as expected.
Solution:
Redirect stderr to separated file and append it to the stdout
file after test-command is executed. Then compare it with
the expected output. This eliminate the assumption that
stdout and stderr must merged in "chronical orders".
The .ddl file are updated by moving all stderr text to the end of the
file.
Platforms tested:
eirene.
|
|
|
|
| |
updated document.
|
|
|
|
|
|
| |
Updated.
Platforms tested:
Eye-balled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Improvement
Description:
The stdout and stderr were both redirected to an output file. This
works fine in tradition sequential Unix machines. But in some
parallel systems (like mpi-jobs in IBM SP), the stderr is merged
with stdout alright but not in the exact order as expected. This
is not deterministic in parallel jobs. So, the test output are
all there but the ordering maynot be as expected.
Solution:
Redirect stderr to separated file and append it to the stdout
file after test-command is executed. Then compare it with
the expected output. This eliminate the assumption that
stdout and stderr must merged in "chronical orders".
Platforms tested:
tested in v1.4. Folded it into v1.5.
|
|
|
|
|
|
| |
Changed the wording of test results.
Platforms tested:
eirene, dangermouse.
|
|
|
|
|
|
|
|
| |
Code cleanup
Description:
Took out a debugging printf
Platforms tested:
FreeBSD 4.4 (hawkwind)
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
check-in the second time to update the handling of data transfer in h4toh5.
This will make up for the cvs conflict checking a couple hours ago.
Description:
Solution:
Platforms tested:
eirene
|