summaryrefslogtreecommitdiffstats
path: root/tools/h5diff
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r18170] Skipped 3 test cases for parallel mode which caused hang.Jonathan Kim2010-01-261-3/+21
| | | | | | | | | They are external-link test cases with following link option. The related code was checked in as svn #18164 and #18165 to support follwing links for h5diff. The test cases will be added back when find solution for parallel mode. Tested on Jam
* [svn-r18166] Purpose:Jonathan Kim2010-01-263-6/+21
| | | | | | | | | | | Take care of test case fail for h5repack from checkin (r18164) Description: Previous checkin didn't allow h5diff to return succeed when a link's target object doesn't exist. Changed it to succeed with warning. (Need to discuss related feature) Tested on Jam
* [svn-r18165] Purpose:Jonathan Kim2010-01-2543-108/+495
| | | | | | | | | | | | Add test cases for h5diff check-in (svn revision #18164). Description: This test cases are for testing comparing through various link combinations relate to bugzilla report 1754. Also improved the test script to handle external link cases and simplified to use single line instead of double for each test cases. Tested on Jam
* [svn-r18164] Purpose:Jonathan Kim2010-01-251-1/+6
| | | | | | | | | | | | | | | Add a feature to compare through links. Relate to bugzilla report 1754. Description: Currently, h5diff command only compares the name(path) of target object not the actual data. With this feature, h5diff will go through the link(s) and figure out the actual object at the end of the link and compare data if exist. Internally we have hard-link, soft-link, external-link (as part of user_defined-link). This feature will provide a user transparent experience when comparing link objects as the user can specify any of those 3 type of links to be compared in any combination. Tested on Jam.
* [svn-r18134] Purpose:Jonathan Kim2010-01-2110-12/+0
| | | | | | | | | | | | Additional fix relted to the fix of bug1672. Description: The fix of bug1672 caused some changes of output which required modifying some test cases. After some discussion, restoring the changes of the test cases was decided. After many experiments for the solution, this fix was made so the code which improved performance can stay. Tested on Jam.
* [svn-r18129] Purpose:Jonathan Kim2010-01-213-2/+13
| | | | | | | Add test case relate to bug1749. Also corrected command echo lines which don't match with actual tests. Tested on Jam.
* [svn-r18107] bug 1673:Albert Cheng2010-01-121-4/+4
| | | | | | | | | | | | | | The mixed use of RUNTEST (original) and RUNTESTS (new) caused confusion. E.g., the timings in test/ was still using the old $RUNTEST. It made more sense to use $RUNTEST which is used by the dejagnu feature of automake. So, I changed all $RUNTEST or $RUNTESTS to $RUNEXEC. config/commence.am & config/conclude.am are the two files that got changes. Also fixed an error in test/Makefile.am. The rest are changed by bin/reconfigure. Tested: h5committested.
* [svn-r18055] Bug fix: 1192Albert Cheng2009-12-262-9/+18
| | | | | | | | Description: Fixed exit code (sometimes return code in Main) to follow the HDF5 standards. Tested: H5committested plus serial test in Jam.
* [svn-r17905] Purpose:Jonathan Kim2009-11-2010-0/+12
| | | | | | | | | | | | | | | | Fix Bug1672 - Display garbage value on LE machine for BE data. Description: Casuing by calling diff_dataset twice when -r or no option was given. Change to call it once which fix the problem. It also improves the performance. (diffing time in half) According further test, it also occurred on BE machine as well and it seems occruing only with the BE data attached to Bugzilla. Don't know how the file was created. Anyway this fix will prevent from diffing with garbage values in similiar potential case. Tested on: linux32 (jam) , linux64 (almani), solaris (linew)
* [svn-r17616] Purpose:Mike McGreevy2009-10-082-9/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CFLAGS overhaul Description: Modified the way configure handles CFLAGS. (note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS). 1. The configure process will now always preserve a user's CFLAGS environment variable setup. Any additional flags necessary for compilation added at configure time will be passed into the Makefiles as AM_CFLAGS, which is an automake construct to be used in addition to CFLAGS. This will allow a user to have the final say, as CFLAGS will always appear later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS during make will no longer completely erase all flags set by configure, since they're maintained in AM_CFLAGS. 2. Additionally, where possible, flags previously being assigned directly into CFLAGS (and thus propagating into h5cc) have now been redirected into H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into the h5cc wrapper script as well. *Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the Makefiles. Complete description of changes and build process will be included in a Configure Document that Elena and I are working on. 3. Removed unsupported config files. This includes: config/dec-osf* config/hpux11.00 config/irix5.x config/powerpc-ibm-aix4.x config/rs6000-ibm-aix5.x config/unicos* 4. Modified configure summary to display additional values. Specifically, appropriate AM_* variables are being shown, as well as H5_FCFLAGS and H5_CXXFLAGS, which were for some reason not already present. Tested: - H5committest - Tested on all THG / NCSA machines, using several combinations of the more prominent configure options (c++, fortran, szip, threadsafe, parallel, et cetera). (Thanks to Quincey for rysnc testing setup!) - With regards to new automated testing, anything *necessary* for compilation will be caught by the daily tests as it stands now. (i.e., if LDFLAGS is not properly set when szip is used, linking will fail). Additionally, with regards to which flags get into h5cc, if any *necessary* flags have been improperly removed, then daily tests should fail during make installcheck. Additional machine-specific desired behaviors and/or checks may have to be set up separately within the daily tests, so this is something to work on.
* [svn-r17606] Code Cleanup:Albert Cheng2009-10-071-8/+1
| | | | | | | | TFLOPS machine has retired long ago. Removed all code specific for its support. Test: h5committested.
* [svn-r17603] Bug fix:Albert Cheng2009-10-061-2/+3
| | | | | | | | | | | The ph5diff tests printout incorrectly reporting they are running h5diff when it actually is running ph5diff. Fixed. Tested: Jam (parallel), linew (serial) No H5committest since it is a shell script and Jam tests both serial and parallel h5diff for Linux while Linew tests Big endian platform.
* [svn-r17466] " Use strict equality as defaultPeter Cao2009-09-1116-339/+143
| | | | | | " Use "--use-system-epsilon" for system EPSILON " Use "-p" or "-d" for whatever user's choice of epsilon " Use "-p 0" or "-d 0" for strict equality (same as default)
* [svn-r17345] Purpose:Mike McGreevy2009-08-121-49/+97
| | | | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Installed new autotools and used them to reconfigure HDF5. - Automake upgraded to 1.11 - Autoconf upgraded to 2.64 - bin/reconfigure script edited to use new versions (on jam), and run to generate new configure script and Makefile.in's. - configure.in script edited to add "_cv_" to all AC_CACHE_VAL strings (in order to comply with new autoconf standard). Tested: Tested on machines jam, smirom, liberty, linew. Tested w/ features c++, fortran, parallel. Tested w/ compilers gcc, pgcc, icc. Further testing via Daily Tests should catch any other outliers. Upon passing DT's, I'll propogate the new tools into 1.8, hdf4, et cetera.
* [svn-r17254] Fixed Bug 1563 - h5diff and Infinity Peter Cao2009-07-286-0/+33
| | | | Added test cases
* [svn-r17228] Purpose:Mike McGreevy2009-07-232-1/+10
| | | | | | | | | | | | | | | | | | | | | | | Fix BZ #1583 Description: The --enable-static-exec flag was broken. Configure was adding the -all-static linker flag to an environment variable which was subsequently never used. (looks like it was used in 1.6 Makefile.ins, but never moved to 1.8's Makefile.ams when we added automake support). To fix, I've added this environment varibale to the link lines of all the tools. Now, when --enable-static-exec is invoked, it will correctly generate statically linked executables in the installed bin directory. Tested: I've tested manually to ensure that the generated execs are static when the flag is used and dynamic when not. I've also tested when szip is used, as this was a use case mentioned in the bug report. Also: ran full tests with make check on jam and smirom for good measure.
* [svn-r17081] Disable hanging invalid files test.Larry Knox2009-06-181-2/+3
|
* [svn-r17058] added some "dummy" declarations for d_statusPedro Vicente Nunes2009-06-162-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | this error home/hdftest/snapshots-hdf5/current/tools/lib/h5tools_ref.c:126: undefined reference to `d_status' happens because the original developer of h5tools_ref.c declared these 2 variables in that source file extern char *progname; extern int d_status; this means that all programs that use this source file (typically all tools) will have to define these 2 variables, even if they are *not* used. examples const char *progname = "h5jam"; int d_status = EXIT_SUCCESS; "progname" is usually used to print the program name in the usage, and "d_status" is just a return value of the tool, usually. I was wondering about removing these 2 declarations from h5tools_ref.c extern char *progname; extern int d_status; and define those variables on each tool if they are only needed (it seems to me that only h5ls and h5dump actually "need" them) tested: smirom parallel
* [svn-r17052] Add a run to the h5repack shell script to read a family filePedro Vicente Nunes2009-06-151-0/+3
| | | | | | | | The file used for input is located in the common source tools for testfiles, in tools/testfiles Modified the h5repack shell script to read files from this location (h5repack reads its input files from a dedicated testfiles location in h5repack/testfiles) Changed the h5diff open file call to use h5tools_fopen, so that it can open all file drivers Tested: windows, linux, solaris
* [svn-r16991] change messages of -c optionPedro Vicente Nunes2009-05-288-11/+11
| | | | tested: windows, linux
* [svn-r16964] bug fix: the phrase "Not comparable" was not being printed for ↵Pedro Vicente Nunes2009-05-201-1/+1
| | | | | | the case of different classes tested: windows, linux
* [svn-r16810] added the words "Not comparable" in the not comparable messagesPedro Vicente Nunes2009-04-2011-16/+16
| | | | tested: linux
* [svn-r16792] Description:Mike McGreevy2009-04-201-4/+4
| | | | | | | | | | | | - Updated bin/reconfigure to use latest version of automake (1.10.2). Re-generated Makefile.in's by running bin/reconfigure. - Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran libraries. Tested: jam, liberty, smirom
* [svn-r16785] added missing test and compare cases inside compounds for nanPedro Vicente Nunes2009-04-181-501/+539
| | | | tested: linux
* [svn-r16614] 3. #1501 (B1) tools bug if dataset is larger than ↵Pedro Vicente Nunes2009-03-254-13/+59
| | | | | | | | | | | | H5TOOLS_BUFSIZE limit. ISSUE : the tools use the following formula to read by hyperslabs: hyperslab_size[i] = MIN( dim_size[i], H5TOOLS_BUFSIZE / datum_size) where H5TOOLS_BUFSIZE is a constant defined of 1024K. This is OK as long as the datum_size does not exceed 1024K, otherwise we have a hyperslab size of 0 (since 1024K/(greater than 1024K) = 0). This affects h5dump. h5repack, h5diff SOLUTION: add a check for a 0 size and define as 1 if so. TEST FOR H5DUMP: Defined a case in the h5dump test generator program of such a type (an array type of doubles with a large array dimension, that was the case the user reported). Since the written file commited in svn would be around 1024K, opted for not writing the data (the part of the code where the hyperslab is defined is executed, since h5dump always reads the files). Defined a macro WRITE_ARRAY to enable such writing if needed. Added a run on the h5dump shell script. Added 2 new files to svn: tools/testfiles/tarray8.ddl, tools/testfiles/tarray8.h5. NOTE: while doing this I thought of adding this dataset case to an existing file, but that would add the large array output to those files (the ddls). The issue is that the file list is increasing. TEST FOR H5DIFF: for h5diff the check for reading by hyperslabs is H5TOOLS_MALLOCSIZE (128 * H5TOOLS_BUFSIZE) or 128 Mb. This makes it not possible to add such a file to svn, so used the same method as h5dump (only write the dataset if WRITE_ARRAY is defined). As opposed to h5dump, the hyperslab code is NOT executed when the dataset is empty (dataset is not read). Added the new dataset to existing files and shell run (tools/h5diff/testfiles/h5diff_dset1.h5 and tools/h5diff/testfiles/h5diff_dset2.h5 and output in tools/h5diff/testfiles/h5diff_80.txt). TEST FOR H5REPACK: similar issue as h5diff with the difference that the hyperslab code is run. Added a run to the shell script (with a filter, otherwise the code uses H5Ocopy). tested: linux (h5commitest failed , apparently it did not detect the code changes in /tools/lib that fix the bug: the error in an assertion in the hyperslab of 0. I am sure that making h5ccomitest --distclean will detect the new code , but don't want to wait more 3 hours :-) )
* [svn-r16561] Purpose:Mike McGreevy2009-03-101-3/+3
| | | | | | | | | | | | | | | | | | Bug Fix Description: Fixing BZ #1381. The --includedir=DIR configure option, which is used to specify the installation location of C header files, did not work correctly as the path was hard-coded in config/commence.am. I'm presuming this is because an older version of automake didn't know where to put c header files. In any case, removing this line now defaults the includedir to the same directory that it is currently hard-coded to, and also fixes the configure flag to allow customization of this value. Tested: jam, liberty
* [svn-r16560] Description:Quincey Koziol2009-03-103-15/+24
| | | | | | | | | | Remove another call to H5E_clear_stack() from within the library. Clean up lots of compiler warnings. Tested on: Mac OS X/32 10.5.6 (amazon) (followup on other platforms forthcoming)
* [svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a ↵Pedro Vicente Nunes2009-02-261-0/+1
| | | | | | | 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
* [svn-r16489] Fixed bug #1459 by eliminating the macro long_long and ↵Allen Byrne2009-02-181-9/+9
| | | | | | | | | | | replacing all instances with long long. Tested: h5comittest fedora 10 x64 Vista 32, VS2005, IVF101 XP32, Cygwin
* [svn-r16461] Bug fix: for compound types, the not comparable test for ↵Pedro Vicente Nunes2009-02-117-2/+74
| | | | | | | | | | | | | | | | | | | | members was not done Solution: for compound types, recursively apply that check Two new cases are added 1) the compound type has a different number of members. Message printed is <obj1> has X members <obj2> has Y members Where X and Y are the number of members of each compound type being compared 2) the compound type has not comparable types (for example a double and an int at the same index) In this case the message Comparison not possible: object1 is of class1 and object2 is of class2 Is replaced with Comparison not possible: object1 has a class1 and object2 has a class2 Modified the test generator program to have these 2 cases Added a shell run for these 2 cases Tested: windows, h5committest
* [svn-r16434] bug fix: typo in usage messagePedro Vicente Nunes2009-02-0515-15/+15
| | | | tested: linux
* [svn-r16358] bug fixPedro Vicente Nunes2009-01-273-3/+4
| | | | | | a new line was not inserted at the end of output, causing diff to complain between linux and frebsd tested: linux , freebsd
* [svn-r16348] #1368 (E1) h5diff: implement "not comparable" messages. ↵Pedro Vicente Nunes2009-01-2635-19/+119
| | | | | | | | Implemented RFC. The new option is <-c, --compare List objects that are not comparable> added some test cases tested: windows, linux
* [svn-r16333] Bug 948 followup.Albert Cheng2009-01-201-2/+2
| | | | | | | Moved a comment up to a more appropriate spot. No execution change. Tested: jam pp.
* [svn-r16328] Bug 948.Albert Cheng2009-01-181-3/+9
| | | | | The test "h5diff -v h5diff_hyper1.h5 h5diff_hyper2.h5" sometimes hangs in THG machines. Skip it until its hanging is resolved.
* [svn-r16300] Added an option to avoid dealing with NaNs Pedro Vicente Nunes2009-01-1315-1/+24
| | | | | | | -N, --nan Avoid NaNs detection Note: there is no shell script run for datasets with NaN because the output is non portable (different results and NaN strings for different systems) Tested: windows, linux
* [svn-r16217] Bug fixPedro Vicente Nunes2008-12-235-2011/+2093
| | | | | | | PG compiler complains about array out of bounds (a rank of zero was not checked) Adding a scalar dataset to the test generator program. this case is run on a previous existing run, the case was added to 2 existing files Tested: windows, linux
* [svn-r16024] For scalar string datasets print the character position when a ↵Pedro Vicente Nunes2008-11-042-504/+504
| | | | | | difference is found instead of a non-existing array position Tested: windows
* [svn-r15988] Merge with 1.8 up to rev 15871Pedro Vicente Nunes2008-10-292-13/+25
| | | | | | Regarding h5diff, h5copy Tested: linux
* [svn-r15987] Merge with 1.8 rev 15871Pedro Vicente Nunes2008-10-2917-102/+36
| | | | | | Eliminate -c option and make that behavior the default and return 2 instead of -1 on error status tested: linux
* [svn-r15979] some test files from rev 15866 from 1.8 branch Pedro Vicente Nunes2008-10-283-0/+2
| | | | tested: linux
* [svn-r15977] merge rev 15866 from 1.8 branch into trunk (diffs for unsigned ↵Pedro Vicente Nunes2008-10-282-0/+19
| | | | | | long long) tested: windows, linux
* [svn-r15942] Purpose: Bug Fixes and Libtool UpgradeMike McGreevy2008-10-241-6/+6
| | | | | | | | | | | | | | | | | | Description: - Remove need to set LD_LIBRARY_PATH when using shared szip library. - Libtool 2.2.6a is now used to generate libraries. - 'make check install' dependency bug is fixed, and should no longer break the build. - removed hard coding of shell in config/commence.am, as this causes problems on Solaris with the new version of libtool. - RELEASE.txt with appropriate changes. Tested: - kagiso, smirom, linew (merged from 1.8, pretty quick tests)
* [svn-r15628] Description:Quincey Koziol2008-09-163-78/+78
| | | | | | | | | | | | | Remove trailing whitespace from C/C++ source files, with the following script: foreach f (*.[ch] *.cpp) sed 's/[[:blank:]]*$//' $f > sed.out && mv sed.out $f end Tested on: Mac OS X/32 10.5.5 (amazon) No need for h5committest, just whitespace changes...
* [svn-r15445] added some commentsPedro Vicente Nunes2008-08-071-0/+6
| | | | tested: windows, linux
* [svn-r15428] http://bugzilla.hdfgroup.uiuc.edu/show_bug.cgi?id=1170Pedro Vicente Nunes2008-08-0418-78/+256
| | | | | | | | | | Summary: when using h5diff to compare the results of h5repack (or other tools that copy one HDF5 file to another), a new option is needed to allow h5diff to make an "absolute" comparison of the 2 files. This is the "contents" mode explained in the usage below. If this mode is present, objects in both files must match (must be exactly the same). If this does not happen, the tool returns an error code of 1 (instead of the success code of 0) Changes to the h5repack test script: the call to h5diff was changed to include -c (maintaining the previous -q). tested: windows, linux, solaris
* [svn-r15246] Changed the shell script to avoid doing a cd $srcdirPedro Vicente Nunes2008-06-2065-391/+96
| | | | | | | | | | | | The name of the files are now given by its full name relative to $srcdir To avoid the printing of the complete full path of the test file, that hides all the other parameters for long paths, the printing of the command line is done first in TESTING with the name only of the test file, not its full path the printing in the expected output that had the file name was removed as well as 3 tests that tested error messages in which the file name was present tested: linux (in 2 different build directories relative to $srcdir), solaris
* [svn-r15238] Pedro Vicente Nunes2008-06-1976-5/+5365
| | | | | | Moved all h5diff testfiles from /tools/testfiles to tools/h5diff/testfiles Tested: linux, solaris
* [svn-r15124] Purpose:Albert Cheng2008-06-021-5/+16
| | | | | | | | | | | | | | bug fixes. Description: Added code to create an empty hdf5 (named h5diff_empty.h5) in order to test if h5diff compares correctly an empty hdf5 vs. a non-empty one. Tested: Tested in kagiso of h5diffgentest itself. Verified by h5dump that h5diff_empty.h5 was indeed empty. Then "h5diff h5diff_empty.h5 h5diff_basic1.h5" returned 0 (should have returned non-zero).
* [svn-r15036] Bug fix.Albert Cheng2008-05-191-4/+4
| | | | | | | | | | | | | | | | | | | Description: The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the Fortran API source so that conclude.am will give fortran api prefix in the test output. The symbox HDF_FORTRAN is also used in configure for a different purpose (indicated --enable-fortran). They conflicted. Similar problem for the symbol HDF_CXX. Solution: Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is a more appropriate name. Same for CXX_API. Along the way, discovered that the Makefile.am of hl/fortran/test and hl/cxx/test did not have those symbols at all. Added them in. Platform tested: Kagiso only. It is a trivia change.
generated by cgit v0.12 at 2024-11-18 07:48:16 (GMT)