hdf5/tools/h5diff/testfiles/h5diff_30.txt

dataset: </dset1> and </dset2>
size:           [6]           [6]
position        dset1           dset2           difference          
------------------------------------------------------------
[ 1 ]          YIN              **INVALID VALUE**
[ 2 ]          **INVALID VALUE** YIN              
[ 5 ]          YIN              YANG             
3 differences found
EXIT CODE: 1
[svn-r20724] Purpose: Fix a bug in h5diff when enum values are compared that do not represent a valid enum value. Description: The h5diff code compares enum values by converting them to strings and then comparing them. When the enum value is out of range and can't be converted to an enum string representation, the comparison was skipped. The code now flags differences when one of the two enum values is out of range (two out of range values are compared in memory). A test has been added to the tools test script. This fixes JIRA HDFFV-7527 Tested on: jam, koala, heiwa (h5committest) 2011-05-05 04:07:38 +08:00			`dataset: </dset1> and </dset2>`
			`size: [6] [6]`
			`position dset1 dset2 difference`
			`------------------------------------------------------------`
			`[ 1 ] YIN INVALID VALUE`
			`[ 2 ] INVALID VALUE YIN`
			`[ 5 ] YIN YANG`
[svn-r20756] Fixes h5diff test failure on BE systems. H5Dread() produces different output for invalid enum type values on systems of different endiannes. On BE systems, it always emits -1. On LE systems, the invalid value is emitted. This difference caused the h5diff test to fail since it tests to see if different invalid enum values are reported as different (on BE systems they are not since -1 == -1). This fix removes the "invalid vs. different invalid" test while we fix the library bug. HDFFV-7527 will be reopened in JIRA until the full test passes. Tested on: jam, heiwa, linew 2011-05-06 03:37:19 +08:00			`3 differences found`
[svn-r20724] Purpose: Fix a bug in h5diff when enum values are compared that do not represent a valid enum value. Description: The h5diff code compares enum values by converting them to strings and then comparing them. When the enum value is out of range and can't be converted to an enum string representation, the comparison was skipped. The code now flags differences when one of the two enum values is out of range (two out of range values are compared in memory). A test has been added to the tools test script. This fixes JIRA HDFFV-7527 Tested on: jam, koala, heiwa (h5committest) 2011-05-05 04:07:38 +08:00			`EXIT CODE: 1`