| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Option is on by default but can be disabled with --disable-shell-testing.
|
| |
|
|
|
|
|
|
|
| |
~HDFTEST/hdf5_hft:hdf5_1_10 to develop"
This reverts commit e9f476dad47ce593f13dacb77b1cc664d1f24e7b, reversing
changes made to 2ff00b1b937ebe36ac6ddf590c16a4c27fc0b053.
|
|
|
|
|
|
| |
Bring README.txt and INSTALL* updates from hdf5_1_10_2 branch to
hdf5_1_10 branch.
Bring bin/release changes to hdff5_1_10 branch.
|
|\ |
|
| |
| |
| |
| | |
generated by autogen.sh are missing, causing chkmanifest to fail.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
over.
Brings coding standards in line with the rest of the library,
enforces better software engineering principles, and makes
everything more maintainable.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
hdf5_1_10
* commit '54957d37f5aa73912763dbb6e308555e863c43f4':
Commit copyright header change for src/H5PLpkg.c which was added after running script to make changes.
Add new files in release_docs to MANIFEST. Cimmit changes to Makefile.in(s) and H5PL.c that resulted from running autogen.sh.
Merge pull request #407 in HDFFV/hdf5 from ~LRKNOX/hdf5_lrk:hdf5_1_10_1 to hdf5_1_10_1
Change copyright headers to replace url referring to file to be removed and replace it with new url for COPYING file.
|
| |
| |
| |
| |
| | |
so that script failures leave the library in a non-compilable state,
making it harder to ignore errors.
|
| |
| |
| |
| | |
then failed to match the pattern after the first run.
|
| |
| |
| |
| | |
Pull version from configure for version test in h5repack_plugin.sh.in
|
| |
| |
| |
| |
| |
| |
| |
| | |
version test expected output file.
Update version on develop branch to 1.11.0.
Please enter the commit message for your changes. Lines starting
|
| |
| |
| |
| |
| | |
* commit 'fded10f0815f593301ac88d08d05343c8077746a':
Add note to bin/release script with hint for situations where files generated by autogen.sh are missing, causing chkmanifest to fail.
|
| | |
|
| |
| |
| |
| |
| | |
so that script failures leave the library in a non-compilable state,
making it harder to ignore errors.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Cimmit changes to Makefile.in(s) and H5PL.c that resulted from running
autogen.sh.
Conflicts:
README.txt
c++/src/Makefile.in
fortran/src/Makefile.in
hl/c++/src/Makefile.in
hl/fortran/src/Makefile.in
hl/src/Makefile.in
java/src/jni/Makefile.in
release_docs/RELEASE.txt
src/Makefile.in
|
| |
| |
| |
| |
| |
| |
| |
| | |
and replace it with new url for COPYING file.
Fix 2 lines in java error test expected output file where messages
include line numbers changed by reducing the copyright header by 2
lines.
|
| |
| |
| |
| | |
HDF5Config.cmake that causes cmake not to find HDF5.
|
|/
|
|
|
| |
Pull version from configure for version test in h5repack_plugin.sh.in
Update version to 1.10.2-snap0 for hdf5_1_10 branch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Comment added to address HDFFV-8270. The sample ontput in the
file's comments are not up-to-date with the scripts in the file
that remove output unique to certain systems when running test
scripts. This output doesn't match expected output files for
the tests, causing them to fail. Ther output_filter.sh file
removes such output. Currently we don't have access to these
systems to update the comments.
testflushrefresh.sh.in:
flushrefresh and other SWMR tests have been failing
occasionally but regularly since bringing them to the develop
branch. The logs and debugging point to unexpected deletion of
signal files as the point of failure, and John Mainzer suggests
that two such tests running simultaneously in the same directory
may lead to the operating system deleting the other test's
signal file. Running the flushrefresh test in its own directory
seems to solve the problem.
|
| |
|
|
|
|
| |
for creating the docs.tar file fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added code to update version strings in
config/cmake/scripts/HDF5config.cmake.
release:
Added options to create CMake tar.gz and zip files containing the
HDF5 source and scripts to build and test HDF5 with cmake and ctest
by running a single command. These were previously assembled
manually.
Added a call to h5vers to set the version being released where it
occurs in files. In particular, the sub-release version string
"currently under development" was not being removed from
cpp_doc_config or HDF5config.cmake.
|
| |
|
|\
| |
| |
| | |
https://bitbucket.hdfgroup.org/scm/~lrknox/hdf5_lrk into develop
|
| |
| |
| |
| |
| |
| | |
HDF5 develop branch. Most of the changes are for the switch from
subversion to it repositories. This copy is not used for THG daily
tests, but is available for testing on remote machines.
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
see if it's enabled, and if it is, call switch_maint_mode -disable
before creating release files, then set it back to enable afterward.
|
| |
|
|
|
|
| |
when git complains about Makefile.in clobbers, etc.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
--short option.
|
|
|
|
| |
allow running h5vers on machines without /usr/hdf/bin/AUTOTOOLS.
|
|
|
|
| |
into tarfiles.
|
|
|
|
|
|
|
| |
* commit '5aee5213190f145b5a734f5dc76a67c82f7d6b82':
emoved .gitattributes and .gitignore, as the manual migration did not create them. Corrected bbrelease script to create new release version with revision hash.
Translate svn commands to git commands for chkmanifest and bbrelease scripts with source in git repository. Removed the -p option from the command to run autogen.sh. It interfered with running chkmanifest on a machine with the correct autotools versions but without access to /usr/hdf/bin/AUTOTOOLS. The autogen.sh script says the option is for HDF group use only and is likely to be removed. The same effect can be achieved by adding /usr/hdf/bin/AUTOTOOLS to the beginning of PATH.
Removed the -p option from the command to run autogen.sh. It interfered with running chkmanifest on a machine with the correct autotools versions but without access to /usr/hdf/bin/AUTOTOOLS. The autogen.sh script says the option is for HDF group use only and is likely to be removed. The same effect can be achieved by adding /usr/hdf/bin/AUTOTOOLS to the beginning of PATH.
|
|
|
|
|
|
|
|
| |
with running chkmanifest on a machine with the correct autotools
versions but without access to /usr/hdf/bin/AUTOTOOLS. The autogen.sh
script says the option is for HDF group use only and is likely to be
removed. The same effect can be achieved by adding
/usr/hdf/bin/AUTOTOOLS to the beginning of PATH.
|
|
|
|
| |
scripts with source in git repository.
|
|
|
|
|
|
|
| |
hl and bin directories
Tested on: 64-bit Ubuntu 15.10 w/ gcc 5.2.1
autotools serial w/ Java, Fortran, & C++
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fortran, java, hl, hl/c++, hl/fortran to so that the shared object version numbers can be incremented independently.
Disabled auto-increment of shared object version numbers by h5vers.
Files modified:
config/lt_vers.am
java/src/jni/Makefile.am
hl/src/Makefile.am
hl/c++/src/Makefile.am
hl/fortran/src/Makefile.am
c++/src/Makefile.am
bin/h5vers
fortran/src/Makefile.am
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rather than HDF5 library version numbers.
Svn revisions reverted: 29341, 29326
Branch features/h5check_version was created for further development.
Files changed
test/tcheck_version.c
test/testcheck_version.sh.in
src/H5public.h
src/H5.c
config/lt_vers.am
bin/h5vers
Tested with h5committest.new
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
library version numbers instead of the library version numbers.
bin/h5vers:
Changed to copy the shared lib version from lt_vers.am to H5public.h
(Thanks to Larry who made the changes.)
config/lt_vers.am:
cosmetic change, nothing material.
src/H5public.h:
Changed by bin/h5vers.
src/H5.c:
Changed H5check_version() to use shared library version for compatibility
checking.
test/tcheck_version.c:
test/testcheck_version.sh.in:
Changed to use shared library version numbers instead of the HDF5 library
version numbers for testing.
Tested: tested in Jam (C only), platypus and osx1010dev (enable fortran and C++).
|
|
|
|
|
|
|
| |
Tested: platypus.
There are still something strange messages during the configure step.
Waiting for Allen to response.
|
|
|
|
| |
Tested on: linux VM
|