| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Added files created by James for user-define links to the command files
Added new script check_h5jam.com to test h5jam/h5unjam; test script
needs more work.
Platforms tested:
VMS server and test script only.
|
|
|
|
|
|
|
|
|
|
| |
Daily test for ttsafe failed on several machines due to the changed error stack.
Solution:
Updated the source code to use new error stack.
Platforms tested:
shanti
|
|
|
|
|
|
|
| |
2. Used to workaround solution to fix the cchunk10 failure caused by the MPICH bug
Machine test:
heping, mir
|
|
|
|
|
|
|
|
| |
independent IO with file setview.
To activite this test,
add the command option -i.
For example, at IBM AIX, type "poe testphdf5 -i" will test the library with independent IO with file setview. It simply replaces all the collective IO tests with independent IO with file setview.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
optimization codes:
1. Provide another option for users to do independent IO with MPI file setview(collectively)
2. With the request of collective IO from users, using Independent IO with MPI file setview if we find collective IO is not good for the applications for IO per chunk(multi-chunk IO) case. Previously we used pure independent IO and that actually performed small IO(IO each row) for this case. The recent performance study suggested the independent IO with file setview can acheieve significantly better performance than collective IO when not many processes participate in the IO.
3. For applications that explicitly choose to do collective IO per chunk case, the library won't do any optimization(gather/broadcast) operations. The library simply passes the collective IO request to MPI-IO.
Tested at copper, kagiso, heping, mir and tungsten(cmpi and mpich)
Kagiso is using LAM, t_mpi test was broken even.
The cchunk10 test failed at heping and mir. I suspected it was an MPICH problem. Will investigate later.
Everything passed at copper.
at tungsten: the old cmpi bug(failed at esetw) is still there. Other tests passed.
Some sequential fheap tests failed at kagiso.
|
|
|
|
|
|
|
|
|
|
|
| |
More tweaks on fractal heap statistics, to better separate information
about managed objects from information about "huge" objects.
Also, clean up some compiler warnings, etc. on 64-bit platforms & Windows.
Platforms tested:
Linux/32 2.6 (chicago)
Linux/64 2.6 (chicago)
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor fields in heap header to clean out information from dropped
features and also group related fields together more nicely.
Add fields to heap header for storing information about "huge" objects.
Platforms tested:
Linux/32 2.6 (chicago)
Linux/64 2.6 (chicago)
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor fractal heap IDs to include "flag byte" as part of the ID. This
byte will be used for the heap ID format version as well as flags to indicate
whether the heap object is a "tiny"/normal/"huge" object (with storage
mechanisms optimized for each type of object).
Platforms tested:
Linux/32 2.4 (chicago)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
|
| |
Add support for entire heap deletion.
Platforms tested:
FreeBSD 4.11 (sleipnir)
Linux/32 2.4 (chicago)
Linux/64 2.4 (mir)
Mac OS X (amazon)
|
|
|
|
| |
locations.
|
|
|
|
| |
Add external link test file
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clean up compiler warnings/failures in test/links.c, especially when
--disable-production flag used with --enable-group-revision
Modify binary dumping in h5dump to clean up files created [a band-aid
solution to not actually creating the files in the srcdir, but better than
just leaving the files around... :-/ ]
Tested:
FreeBSD 4.11 (sleipnir) (w/ configure flags above)
Too minor to require h5committest
|
|
|
|
|
|
|
|
|
| |
Re-run 'make trace' on this file, so API tracing doesn't issue compiler
errors in development builds
Tested:
FreeBSD 4.11 (sleipnir)
Too minor to require h5committest
|
| |
|
|
|
|
|
|
| |
nosuchfile.ls is the expected output.
Tested: tg-ncsa and heping.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fixes.
Description:
There were MPI_init and MPI_finalize calls in the code of h5tools_fopen in
parallel mode. But if a non-MPI tool is invoke to open a non-existing
file, it tries to open the non-existing file with different VFD and
eventaully came to try with the MPIO or the MPIPOSIX vfd, then it would
try to do MPI_Init which would fail in the MPI environment if the a.out
was not launched by MPI properly.
Solution:
MPI_Init and MPI_Finalize in general should be called by the MPI application,
not called by a library subroutine as in the manner that was done here.
Removed the MPI_init and MPI_Finalize calls. Used MPI_Initialized to
verify if this has been launched as an MPI application in the proper
manner before attempting to use the MPIO or the MPIPOSIX VFD to open
the file.
Tested:
In tg-ncsa parallel, where it had failed explicitly and also in Heping,
using both serial and parallel mode.
|
|
|
|
|
|
| |
using a
LAPL. Now there are H5Pget and H5Pset functions for "elink_prefixes".
|
|
|
|
|
|
| |
Found two minor bugs in h5dumpgentst.c and links.c. Have informed James. Should work with windows.
Tests with MSVS 6.0 with visual fortran 6.6c.
|
|
|
|
|
|
|
| |
used inconsistently
(the nlinks property was an int in some places and a size_t elsewhere--it is now
a size_t everywhere).
|
| |
|
|
|
|
|
|
| |
builds (not sure
why they weren't on other systems). Thanks, Kent!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Users can create external links using H5L_create_external(). These links
point to an object in another HDF5 file. Users can alter the behavior of
external links or create new kinds of links by registering callbacks
using the H5L interface.
Added tests, tools support, etc.
Also a number of other, minor changes have been made (some restructuring of
the H5L interface, for instance).
Additional documentation and examples are forthcoming.
|
|
|
|
|
|
|
|
| |
Added test script to test h5import tool; added new source file
to the make.com file in the src directory.
Platforms tested:
Only h5import was tested on the VMS server
|
|
|
|
|
|
|
|
|
|
|
| |
Refactored free space manager to use metadata cache for serialized free
space sections. This speeds up the fractal heap test considerably...
Tested:
FreeBSD 4.11 (sleipnir)
Linux 2.4/32 (chicago)
Linux 2.4/64 (mir)
Mac OS X (amazon)
|
|
|
|
|
|
| |
the DT from
dying again.
|
|
|
|
|
|
|
| |
Added command files to compile and test h5copy tool.
Platfroms tested:
VMS server
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
using
the $srcdir properly. It is not right to chdir into testfiles and write
files there because in real srcdir mode, one should not changes things
in the srcdir area which could be shared by multiple builds simultanteously.
Solution: added the proper $srcdir components to the source file name.
Also clean up the indentation by cb.
Tested: only by hand in heping.
|
|
|
|
|
|
|
|
|
| |
ttsafe test failed on the tts_error call. The error was due to the outdated
expected error stack; fixed.
Test was also moved to use new error APIs.
Platforms tested: Linux 2.4 (heping) and Solaris 2.9 (shanti)
|
|
|
|
|
|
| |
added a call to h5tools_close
tested: linux
|
|
|
|
|
|
|
|
|
|
| |
"make check-vfd" will now run all tests in the test directory with different
file drivers (at least, all of those tests that use the testing framework's
FAPL). Tests that fail will be skipped.
This is not a perfect fix, but is better than nothing.
Along with this change, check-vfd should be added to the Daily Tests.
|
|
|
|
|
|
|
| |
1. changed the -F flag option names to "BE and "LE" for big and little endian
2. added a more verbose usage message for these options
3. add a new test
4. add a make clean instruction to *.bin
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the last scattered bunch of problems with the object deletion code,
which appears to be completely working now (for objects that are stored
within heap blocks - standalone objects aren't implemented yet).
Also, re-work the regression test to speed up some of the existing tests
and add in 100-200 more combinations of tests - overall, its probably even
slower than it was... :-/
Tested:
FreeBSD 4.11 (sleipnir)
Linux 2.4 (chicago)
Mac OS X (amazon)
|
|
|
|
|
|
| |
updated the usage message with new info for the binary output option
tested: linux
|
|
|
|
|
|
| |
the tests.
This command script cannot tell reliably if tests passed. More work is needed.
|
|
|
|
|
| |
new feature
h5dump binary output. use little and big endian type conversions
|
| |
|
|
|
|
|
|
| |
build the tool.
Test command file is not quite working yet.
|
|
|
|
| |
test: linux
|
|
|
|
| |
All tests passed on the VMS server.
|
| |
|
|
|
|
| |
Now delete them. Sorry for the mistake.
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug fix
calling h5tools_get_fapl running the mpio driver caused H5FD_pl_copy to
fail silently in some conditions. a MPI call was made before MPI_Init.
solution: corrected the MPI call to be made after MPI_Init and added error return
conditions to H5FD_pl_copy and h5tools_get_fapl
tested on copper parallel, mir, shanti
|
|
|
|
|
|
| |
This will generate h5copy on windows.
The previous check-in is under the wrong directory.
|
|
|
|
| |
This will generate h5copy on windows.
|
|
|
|
|
|
|
|
|
|
| |
h5ls uses -S flag to display datatype in a machine-readable form. Since
VMS is not a case sensitive system, triple quotes around S are needed; fixed.
h5ls -w80 -v -S tattr2.h5
test still reports failure due to line 311 in the tattr2.ls file "Modified: XXXX..."
Document it for now in the command file.
|
| |
|
|
|
|
|
|
| |
Updating all.dsw,all.sln(for command-line testing only) and binread.dsp.
New projects have been added into.
|
|
|
|
|
|
|
|
|
|
| |
except for
the last one
h5ls -w80 -v -S tattr2.h5
h5ls prints "native" for all types instead of the complete datatype definition.
I will look into the problem next.
|
|
|
|
|
|
| |
included.
Forgetting updating MANIFEST may be the reason why alpha release doesn't include binread.dsp and causes the problem on windows.
|
|
|
|
|
|
|
|
|
|
| |
Checkpoint further work on object deletion code for fractal heaps. I
believe everything is finally working for this sub-task. More regression tests
soon, but I don't foresee any problems.
Machines:
FreeBSD 4.11 (sleipnir)
Linux 2.4 (chicago)
|