Maintenance for alpha5 release; brought command files up-to-date.
Platforms tested:
VMS server. Compilation, C++, F90 and tools tests passed;
C tests are still running.
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.
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
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.
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.
Description: Some "" were missing causing incorrect results in passing an argument
string.
Solution: Added missing ""
Platforms tested: VMS server.
There are still problems with the tests that have
"string" as an argument, for example:
-d "/g1/g1.1/dset1.1.2[0;2;10]" tall.h5
On VMS "g1" and "dset" are translated in upper case causing h5dump
to fail. After figuring out the correct amount of " for VMS I encountered
another problem: corresponding DDL file does not have "" around
/g1/g1.1/dset1.1.2..... and therefore VMS diff fails.
Question: Since command to h5dump is
h5dump -d "/g1/g1.1/dset1.1.2[0;2;10]" tall.h5, why the second line in the
tall-5s.ddl has
h5dump -d /g1/g1.1/dset1.1.2[0;2;10] tall.h5? If one types the command
without "", it fails on UNIX.
Misc. update:
Description: More work on the test script: added all current UNIX tests.
Solution:
Platforms tested: VMS server; many tests failed but I think it is false negative.
will investigate, but for now, let's save the code.
Misc. update:
Description: Added a command file for testing tools; it has a framework
to do exactly (almost) what UNIX tools test scripts do:
- run test tool and save output
- compare output with expected result
- figure out the difference and
- print PASSED /*FAILED* in a manner similar to the UNIX output
It needs to be populated with more tests and reused for other tools.
Solution:
Platforms tested: VMS server
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: Some VMS command files were broken, some needed
an update to catch up with the current code distribution.
Solution: Fixed
Platforms tested: VMS server with IEEE option. Will do more testing after
checking out a fresh CVS version.
Misc. update:
Description: Some dumper tests suppose to fail; those tests cause make file
to exit.
Solution: For now I commented those tests to let other tests
to run; output is saved in a file for examination. Next step
will be to compare with the existing output. (Actually
the next step will be to learn how to program functions in DCL to
create a test script similar to UNIX one, but at least I finally
figured out why the test script was exiting.)
Platforms tested: VMS server
Misc. update:
