Commit Graph

6 Commits

Author SHA1 Message Date
Jonathan Kim
af749bafb7 [svn-r19051] Purpose:
Add --no-dangling-links option to h5ls. 

Description:
Related to "Bug 1830 - Following an dangling external link in h5ls should set non-zero return code."
If --no-dangling-links option is specified and any dangling link is found, return exit code 1 (error).

Tested:
 jam, amani and heiwa
2010-07-07 13:52:04 -05:00
Albert Cheng
ed9a9f8c50 [svn-r18985] Test feature: (bugs 1919)
Problem: some launching command like yod (and sometimes mpirun), do not pass
back the exit code of the executables back to the shell. It always returns 0
if it can launch the executable. This cause tests that expect non-zero exit
code to fail incorrectly.

Short term Solution:
Added the feature that if $RUNSERIAL_NOEXITCODE is defined, do not
test conditions that rely on non-zero exit code.

Tests:
dove-linux using RUNSERIAL=thgyod to see the failures and using
$RUNSERIAL_NOEXITCODE=yes to bypass the errors.
Also h5committested.
2010-06-08 13:22:11 -05:00
Albert Cheng
21d186a8e7 [svn-r18984] Description:
Fixed exit code (sometimes return code in Main) to follow the HDF5 standards.

Tested:
Tested in Dove-linux only since change is trivial and has passed in v1.8.
2010-06-07 18:44:27 -05:00
Jonathan Kim
1a02e37f16 [svn-r18943] Purpose:
Support follow symbolic links.

Description:
    Add '--follow-symlinks' option to follow symbolic links (soft and external).
    Update help page according to RM.
    Remove some warning messages from compiler.

Tested:
    jam, amani and linew
2010-06-02 10:13:13 -05:00
Jonathan Kim
5edb7aabe4 [svn-r18642] Purpose:
Fix for Bug 1793 - h5ls on a non-existent file gives 0 return code

Description:
    After the fix, h5ls returns 1 (EXIT_FAILURE) if non-existent file is given.

Tested:
    jam, amani, linew
2010-04-27 15:22:48 -05:00
Pedro Vicente Nunes
f8c5384aa5 [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output)
the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms  ("32-bit little-endian integer" would be printed instead).  Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other
tested: h5committest
2009-02-26 15:21:50 -05:00