Larry mentioned that intel compiler was used on Mac for testing.
Allen requested comment it out.
"It is not scheduled for 1.8, I created the file for Java testing. Actually I
have to create windows versions because of the use of floating point." - Allen
It goes down to the error handling branch and prints "FAILED". The fix is adding "return 0;" in the end of the function.
Tested on jam - simple change.
HDFFV-8012 - h5repack changes max dims and cause failure if only "-f none" is used without changing layout for chunked dataset when a chunk dim is bigger than a dataset dim
Description:
"h5repack -f <obj>:NONE <file.h5> out.h5" command failed if source file contains chunked dataset and a chunk dim is bigger than a dataset dim.
Another issue is that the command changed max dims if chunk dim is smaller than the dataset dim.
These issue occurred when dataset size is smaller than 64k (compact size limit)
Fixed them.
Tested:
jam (linux32-LE), koala (linux64-LE), ostrich (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE), Windows (32-LE cmake), cmake (jam)
distribute by the author. It was an example program showing how to measure
parallel IO speed. Since then, we have created h5perf to do I/O performanace
measurement. This example is not needed any more.
mpi-perf.c:
Removed.
Makefile.am:
Makefile.in:
Removed the entry of mpi-perf.c so that "configure --enable-build-all ..."
will not build it.
The change is trivial that I got permission to skip the code review step.
Tested: h5committest plus "--enable-parallel --enable-build-all" in koala.
Use
LT_PREREQ([2.2])
LT_INIT([dlopen])
instead of
AC_LIBTOOL_DLOPEN
AM_PROG_LIBTOOL
Also add ALLOW_UNSUPPORTED on threadsafe check
Both from 1.8 configure
Propogate Coverity changes to trunk, also fix compiler warnings and
other minor code cleanups. (QK & JK)
r20393: (Not directly propogated, since trunk also had a similar fix)
Move initialization ocrt_info.new_obj = NULL; before FUNC_ENTER_NOAPI -- gh
r20397:
Added free(src_sizes) --gh
r20398:
Added free(src_offset). --gh
Tested on:
Mac OSX/64 10.7.4 (amazon) w/debug, parallel, FORTRAN & C++
(h5committest forthcoming)
HDFFV-8143 Provide a routine(s) for telling the user why the library broke collective data access
Description:
Fixed Daily test failed from the previous commit r22735. (ember)
Also changed H5Pget_mpio_no_collective_cause() parameter type from
H5D_mpio_no_collective_cause_t to uint32_t due to change to return
combined bitmap value which can be not emun defined value.
Tested:
jam (linux32-LE), koala-pp (linux64-LE), ember, h5committest
Bring generic improvements from encode/decode property list branch to
the trunk. This includes a better version of the property list comparison
routine, cleaned up compiler warnings, and some cleaned up property list
callbacks. Also, started on changes to clean up parallel test output, so that
it doesn't report successful tests from each process.
Tested on:
Mac OSX/64 10.7.4 (amazon) w/debug, GCC 4.7.x, FORTRAN, C++, threadsafe and parallel
Linux 2.6/32 (jam) w/debug
Solaris 2.7/64 (linew) w/debug
HDFFV-5919 - GMQS: h5diff - The number of object difference is not consistent between dataset and group/type when attribute(s) have differences
Description:
Object differences are not consistent between dataset and group/datatype when their attribute(s) have differences. This is because attribute(s) differences is not accumulated to group or datatype object’s difference, but accumulated to dataset difference.
To fix, do not accumulate attribute difference to dataset difference. This is referred to h5diff’s default behavior and also past report from users that users were confused by the accumulated behavior. (also can’t figure out only for dataset difference , also hard to spot dataset difference when it has lots of attributes or differences)
This also lead to fix inconsistent format indicating difference between dataset and group/datatype object.
Tested:
jam (linux32-LE), koala (linux64-LE), ostrich (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE), Windows (32-LE cmake), cmake (jam)
Fix for HDFFV-7959 H5Rdereference should check for default (HADDR_UNDEF) value and not continue processing and return so that ret value can be checked and handled properly.
Added fix and test, reviewed:
Tested: jam (gnu, intel)
HDFFV-8143 Provide a routine(s) for telling the user why the library broke collective data access
Description:
Daily test failed from the previous commit r22735. (ember)
Skip tests not to disrupt other tests while finding a solution for ember.
HDFFV-8143 Provide a routine(s) for telling the user why the library broke collective data access
Description:
Daily test failed from the previous commit r22735. (ember)
Follow actual_io function to sync before go futher as this is similar
function.
Tested:
jam (linux32-LE), koala-pp (linux64-LE), ember
HDFFV-8143 Provide a routine(s) for telling the user why the library broke collective data access
Description:
Daily test failed from the previous commit r22735. (koala , ember)
Fixed failure due to not be able to read external-storage file from external test.
Tested:
jam (linux32-LE), koala-pp (linux64-LE)
HDFFV-8143 Provide a routine(s) for telling the user why the library broke collective data access
Description:
Added H5Pget_mpio_no_collective_cause() function that retrive reasons why the collective I/O was broken during Read/Write IO access.
Reasons to break collective I/O:
- SET_INDEPENDENT
- DATATYPE_CONVERSION
- DATA_TRANSFORMS
- MPIPOSIX
- NOT_SIMPLE_OR_SCALAR_DATASPACES (NULL Space)
- POINT_SELECTIONS
- NOT_CONTIGUOUS_OR_CHUNKED_DATASET (Compact or External-Storage)
- FILTERS
Tested:
jam (linux32-LE), koala (linux64-LE), ostrich (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE)
