summaryrefslogtreecommitdiffstats
path: root/test/ttsafe_error.c
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r27777] merge from trunk.Mohamad Chaarawi2015-09-141-0/+1
|\
| * [svn-r27587] Added a new API call (H5is_library_threadsafe) to the library. ↵Dana Robinson2015-08-261-0/+1
| | | | | | | | | | | | | | | | | | | | This call can be used to determine at runtime if the library was built with thread-safety. Fixes HDFFV-9496 Tested on: h5committest
* | [svn-r27141] merge from trunk.Mohamad Chaarawi2015-06-031-3/+3
|\ \ | |/
| * [svn-r27133] - Add a new attribute function characterstic for format:Mohamad Chaarawi2015-06-011-3/+3
| | | | | | | | | | | | | | | | * H5_ATTR_FORMAT(X,Y,Z) __attribute__((format(X, Y, Z))) - Rename UNUSED attribute characterstic to H5_ATTR_UNUSED. - Rename NORETURN attribute characterstic to H5_ATTR_NORETURN tested with h5committest.
* | [svn-r25452] realign tests with trunk.Mohamad Chaarawi2014-07-211-1/+0
| |
* | [svn-r24044] Merging r23833 through r24043 from trunk.Mohamad Chaarawi2013-08-211-3/+1
|\ \ | |/
| * [svn-r24030] Description:Quincey Koziol2013-08-191-1/+1
| | | | | | | | | | | | | | | | Clean up more compiler warnings. Tested on: Mac OSX/64 10.8.4 (amazon) w/gcc, C++ & FORTRAN (too minor to require h5committest)
| * [svn-r24020] Description:Quincey Koziol2013-08-171-2/+0
| | | | | | | | | | | | | | | | Clean up compiler warnings Tested on: Mac OSX/64 10.8.4 (amazon) w/C++ & FORTRAN (too minor to require h5committest)
* | [svn-r22903] update the expected error list in the thread safe error tests ↵Mohamad Chaarawi2012-10-161-10/+17
|/ | | | to reflect the existence of the VOL layer noe
* [svn-r19481] I'm backing out my fix for bug 1707 because there're some ↵Raymond Lu2010-09-271-16/+4
| | | | | | | | | | | unresolved issues - r19441 and 19467. Bug 1707 is that H5Eset_auto causes a seg fault when an application uses -DH5_USE_16_API with the 1.8 library to compile. I created a branch off the trunk called set_auto to continue working on the problem. Tested on jam - backing out, simple.
* [svn-r19457] Bug fix for 1707 - H5Eset_auto causes a seg fault when an ↵Raymond Lu2010-09-211-4/+16
| | | | | | | | | | | | | application uses -DH5_USE_16_API with the 1.8 library to compile. The cause is from the mismatch of H5Eprint1 and H5Eprint2 set through H5Eset_auto. I changed the union in the structure H5E_auto_t. Another change is to make H5Eget_auto fail if H5Eset_auto is called to set the printing function. I'll write a document for it. Tested on heiwa, jam, and amani. The property change in configure.in, config, and Makefile.am came from the merge of the 1.8 library change.
* [svn-r19367] Purpose:Mike McGreevy2010-09-101-20/+13
| | | | | | | | | | | | | | | | | | | Add windows threads support to HDF5. Description: Added calls to the windows threads library to the H5TS layer, and wrapped most calls to either pthreads or windows threads library with portable H5TS-style defines. Modified tests to use portable function definitions as well. This can be configured via CMake with the HDF5_ENABLE_THREADSAFE option, and should work on windows vista and later operating systems. Tested: h5committest, plus threadsafe with pthreads on jam and amani, and tested on a Windows Vista VM with threadsafe using windows threads.
* [svn-r15628] Description:Quincey Koziol2008-09-161-3/+3
| | | | | | | | | | | | | 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-r14199] Description:Quincey Koziol2007-10-111-11/+11
| | | | | | | | | | | | | | | | | | | | | Add H5Dcreate to API versioned routines, replacing internal usage with H5Dcreate2 Fix thread-safe error stack initialization for API versioned error stack printing routines. Tested on: FreeBSD/32 6.2 (duty) in debug mode FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Mac OS X/32 10.4.10 (amazon) in debug mode
* [svn-r14193] Description:Quincey Koziol2007-10-081-2/+2
| | | | | | | | | | | | | | | | | | | Make H5Dopen versioned and change all internal usage to use H5Dopen2 Add simple regression test for H5Dopen1 Tested on: FreeBSD/32 6.2 (duty) in debug mode FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Mac OS X/32 10.4.10 (amazon) in debug mode
* [svn-r13650] Description:Quincey Koziol2007-04-121-7/+7
| | | | | | | | Clean up problems from error handling API changes in parallel and threadsafe builds. Tested on: FreeBSD/64 6.2 (liberty) w/parallel & threadsafe
* [svn-r13639] Description:Quincey Koziol2007-04-111-7/+10
| | | | | | | Accomodate changes in error stack for recent library code changes. Tested on: Linux/64 2.6 (chicago2) w/threadsafe
* [svn-r13253] Updated all C and C++ style source code files with the THG ↵Albert Cheng2007-02-071-2/+3
| | | | | | | | | copyright notice. Tested platform: Kagiso only since it is only a comment block change. If it works in one machine, it should work in all, I hope. Still need to check the parallel build on copper.
* [svn-r12632] Description:Elena Pourmal2006-08-271-9/+9
| | | | | | | | | | Thread safe error test fails due to the changes in the error stack. Solution: Updated the expected error stack. Platforms tested: heping (too minor, probably will fail on Tuesday anyway)
* [svn-r12558] Problem:Elena Pourmal2006-08-091-5/+5
| | | | | | | | | | 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
* [svn-r12521] Description:Elena Pourmal2006-07-311-11/+11
| | | | | | | | | 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)
* [svn-r11712] Purpose:Quincey Koziol2005-11-151-10/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New feature Description: Check in baseline for compact group revisions, which radically revises the source code for managing groups and object headers. WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! This initiates the "unstable" phase of the 1.7.x branch, leading up to the 1.8.0 release. Please test this code, but do _NOT_ keep files created with it - the format will change again before the release and you will not be able to read your old files!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! WARNING!!!! Solution: There's too many changes to really describe them all, but some of them include: - Stop abusing the H5G_entry_t structure and split it into two separate structures for non-symbol table node use within the library: H5O_loc_t for object locations in a file and H5G_name_t to store the path to an opened object. H5G_entry_t is now only used for storing symbol table entries on disk. - Retire H5G_namei() in favor of a more general mechanism for traversing group paths and issuing callbacks on objects located. This gets us out of the business of hacking H5G_namei() for new features, generally. - Revised H5O* routines to take a H5O_loc_t instead of H5G_entry_t - Lots more... Platforms tested: h5committested and maybe another dozen configurations.... :-)
* [svn-r11276] Purpose:Quincey Koziol2005-08-201-20/+22
| | | | | | | | | | | | | | Code cleanup/bug fix Description: Add missing files to manifest Remove C++ style single-line comment from recent checkin and also re-indent in a few places. Platforms tested: FreeBSD 4.11 (sleipnir) w/thread-safe Not configured w/h5committest
* [svn-r11268] Purpose:Fang Guo2005-08-191-15/+38
| | | | | | | | | | | Improvement Description: Add some assertion statements to locate the errors when they happen Solution: Platforms tested: MSVS 6.0 on windows and heping(with pthread) Misc. update:
* [svn-r11245] Purpose:Quincey Koziol2005-08-131-9/+9
| | | | | | | | | | | | | | | | | | | | Code cleanup Description: Trim trailing whitespace, which is making 'diff'ing the two branches difficult. Solution: Ran this script in each directory: foreach f (*.[ch] *.cpp) sed 's/[[:blank:]]*$//' $f > sed.out && mv sed.out $f end Platforms tested: FreeBSD 4.11 (sleipnir) Too minor to require h5committest
* [svn-r9727] Purpose:Quincey Koziol2004-12-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug Fix/Code Cleanup/Doc Cleanup/Optimization/Branch Sync :-) Description: Generally speaking, this is the "signed->unsigned" change to selections. However, in the process of merging code back, things got stickier and stickier until I ended up doing a big "sync the two branches up" operation. So... I brought back all the "infrastructure" fixes from the development branch to the release branch (which I think were actually making some improvement in performance) as well as fixed several bugs which had been fixed in one branch, but not the other. I've also tagged the repository before making this checkin with the label "before_signed_unsigned_changes". Platforms tested: FreeBSD 4.10 (sleipnir) w/parallel & fphdf5 FreeBSD 4.10 (sleipnir) w/threadsafe FreeBSD 4.10 (sleipnir) w/backward compatibility Solaris 2.7 (arabica) w/"purify options" Solaris 2.8 (sol) w/FORTRAN & C++ AIX 5.x (copper) w/parallel & FORTRAN IRIX64 6.5 (modi4) w/FORTRAN Linux 2.4 (heping) w/FORTRAN & C++ Misc. update:
* [svn-r9234] Purpose:Quincey Koziol2004-09-091-36/+2
| | | | | | | | | | | | | | | | | | | | | | | Code cleanup Description: Tweak recent "forward compatibility" changes to the H5E* API (which allowed for the old H5E API functions to remain unchanged) by allowing for the error stack callback function (H5E_auto_t) to also remain unchanged from the 1.6 branch. This required changing the H5E{get|set}_auto routines to have the old style H5E_auto_t type (which didn't have a stack ID parameter) and the new H5E{get|set}_auto_stack routines to have a newer "H5E_auto_stack_t" type (which has a stack ID parameter). This should make the H5E API changes as forwardly compatible as possible. One side-affect of this change was that it was impossible to determine if the current auto error callback was the old style (H5E_auto_t) or the new style (H5E_auto_stack_t) of callback, so a new API function (H5Eauto_is_stack) was adde to query this. Platforms tested: FreeBSD 4.10 (sleipnir) IRIX64 6.5 (modi4) h5committest
* [svn-r9221] Purpose: Bug fixRaymond Lu2004-09-081-1/+1
| | | | | | | | Description: One place was left out for update after the Error API was modified. Changed it from H5Eset_auto to H5Eset_auto_stack. Platforms tested: sleipnir(with threadsafe) - simple change.
* [svn-r9208] Purpose: Bug fixRaymond Lu2004-09-041-3/+3
| | | | | | | | Description: A few items were left out when tried to restore the old Error API. There are also a few minor bug fixes. Platforms tested: arabica fuss h5committest.
* [svn-r8048] Purpose:Quincey Koziol2004-01-101-14/+7
| | | | | | | | | | | | | Code cleanup & reorganization Description: Move further in the testing framework cleanup, eliminating all the global variables (moving them into testframe.c as static variables) from the testing framework code and moving it into the libh5test.a. Platforms tested: FreeBSD 4.9 (sleipnir) w & w/o thread-safety, c++ & parallel h5committested
* [svn-r7527] Purpose:Quincey Koziol2003-09-301-2/+8
| | | | | | | | | | | | Code cleanup Description: Clean up a few loose ends and warnings for the 1.6 compatibility changes to the error API. Platforms tested: FreeBSD 4.9 (sleipnir) too minor to require h5committest
* [svn-r7520] Purpose: bug fixRaymond Lu2003-09-291-2/+30
| | | | | | | | | Description: add backward compatibility for thread safety Platforms tested: RH 8(fuss) Misc. update:
* [svn-r7311] Purpose:Quincey Koziol2003-08-081-151/+129
| | | | | | | | | | | | | Bug fix Description: Corrected thread-safe error checking tests to use per-thread 'automatic error' callbacks. Also, minor code cleanups Platforms tested: h5committested
* [svn-r7265] *** empty log message ***Raymond Lu2003-07-261-28/+59
|
* [svn-r7109] Purpose:Quincey Koziol2003-06-261-3/+1
| | | | | | | | | | | Code cleanup Description: Clean up varios compiler warnings flagged by SGI compiler and gcc 3.3 Platforms tested: FreeBSD 4.8 (sleipnir) h5committest
* [svn-r6538] Purpose:Bill Wendling2003-03-311-0/+14
| | | | | | | | | | | | | Update Description: Updated the Copyright statement Platforms tested: Linux (This change is only in the comments, so I just check that the modules still compile) Misc. update:
* [svn-r6386] Purpose:Quincey Koziol2003-02-101-0/+2
| | | | | | | | | | | | | | Bug fix Description: The "system scope" for threads isn't supported on all platforms. Solution: Add detection of this feature to the configure script and check for "H5_HAVE_SYSTEM_SCOPE_THREADS" in the appropriate places. Platforms tested: modi4 w/threadsafe
* [svn-r6383] Purpose:Quincey Koziol2003-02-071-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New feature for developers. Description: Added "function stack" tracing to library. This allows developers (there is no public API) to call H5FS_print within the library and get a listing of the functions traversed to reach that point in the library. Eventually, I may add support for reporting the parameters to each function also... Mainly for debugging parallel I/O programs, but I think it will come in handy in other cases also. The function stack tracking is controlled with a configure switch: --enable-funcstack, which defaults to enabled currently. When we branch for 1.6, we should change the default setting on the branch to be disabled. Also, added a destructor to the thread-specific keys when thread-safety is turned on in the library. Otherwise, they were leaking memory and causing difficult to debug errors in threaded programs (like the test/ttsafe test). Platforms tested: Tested h5committest {arabica (fortran), eirene (fortran, C++) modi4 (parallel, fortran)} FreeBSD 4.7 (sleipnir) w/thread-safety enabled. Misc. update: Updated MANIFEST with new files added (src/H5FS.c & src/H5FDprivate.h) Update release_docs/RELEASE with thread-safety bug fix.
* [svn-r6263] Purpose:Quincey Koziol2003-01-101-2/+7
| | | | | | | | | | | | | | | Update test Description: Some of the performance improvements changed the errors that are reported for creating a duplicated dataset in a file, causing this test's hard-coded errors to check for to fail. Solution: Updated error stack reported for dataset creation failure. Platforms tested: FreeBSD 4.7 (sleipnir) w/threads
* [svn-r4464] Bill Wendling2001-09-181-3/+3
| | | | | | | | | | | Purpose: Bug Fix Description: The error codes checked for were hardcoded into the program. Solution: Used the "enum" names instead. Platforms tested: Linux
* [svn-r4419] Bill Wendling2001-09-041-13/+19
| | | | | | | | | | | | | | Purpose: Bug Fix Description: The table of error messages was updated in H5E.c. The change wasn't reflected in this test because, sadly, we use hardcoded numerical values for the "error" we want to check for and not the symbols. Solution: Bumped up the error number from 32 to 34 to coincide with the error we expect. Platforms tested: Linux
* [svn-r2287] Changed ttsafe_* test files so that they create their own HDF5 ↵Bill Wendling2000-05-191-125/+135
| | | | | | | | file (they were only creating one for all of them). Also changed so that, if they got an error, it actually specifies that the tests failed on the screen instead of succeeded ;-)
* [svn-r2264] Added Thread-safe feature. This is the phase 1 implementationChee-Wai Lee2000-05-181-0/+179
that all HDF5 API functions are protected by a mutex lock. Basically, serialized all API calls. To use it, use configure --enable-threadsafe --with-pthread
generated by cgit v0.12 at 2024-07-09 11:14:20 (GMT)