summaryrefslogtreecommitdiffstats
path: root/testpar/t_posix_compliant.c
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r11798] Purpose:Albert Cheng2005-12-161-0/+17
| | | | | | | | | | | Feature. Description: Modified it so that it can be compiled outside of HDF5 library as a standalone program. e.g., mpicc -DSTANDALONE prog.c. Platforms tested: Tested in Red storm and heping.
* [svn-r11788] Purpose:Albert Cheng2005-12-121-2/+5
| | | | | | | | | | | | | | | | | | Patch. Description: Copper would fail with a message of 0032-113 Out of memory in routine unknown, task 0 when run with 3 processes and size 1MB in MPI-IO tests. It seems to be a copper MPIO error. Solution: Reduced the upper bound of default write size to 1/2MB (but tests only go to 1/4MB) for now, pending permenant fix from Copper. Platforms tested: Copper.
* [svn-r11786] Purpose:Leon Arber2005-12-111-18/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Minor bug fixes. Description: 1. Changed free() calls to HDfree() 2. Corrected behavior of -m command-line parameter 3. Changed return value to always return 0. Solution: 2. The -m flag tells the test to run only the MPI IO tests. However, it would incorrectly make the test run both the MPI and POSIX tests (same as the default behavior). 3. This test is known to fail on many platforms, and, even on those platforms where it usually passes, it is known to suffer transient failures (especially with small test file sizes). It's outcome is also very dependent on the filesystem on which the testfile is created. Corrected the program to always return success, so that it doesn't interfere with the daily tests. The motivation for this is that this test has nothing to do with the HDF library and is an auxiliary test. Failures in t_posix_complaint do not necessarily mean that parallel HDF will fail, but simply indicate something to look into, especially on new platforms. This is now an "output only" test, and any errors will be only be visible in the output. Platforms tested: copper (all of these were minor changes) Misc. update:
* [svn-r11783] Purpose:Albert Cheng2005-12-111-16/+32
| | | | | | | | | | | | | | | | bug fix. Description: Fixed the segmentation fault errors in modi4, copper and tg-login. It was due to the misuse of trying to realloc a pointer returned by getenv_all. (not supposed to.) Also rearranged the code so that option is checked first, then check with environment variable, then use default setup. This saves the need to do realloc at all. Platforms tested: Heping, modi4, shanti, copper (copper showed a different error now.)
* [svn-r11778] Purpose:Leon Arber2005-12-081-7/+9
| | | | | | | | | | | | | | | | | Bug fix. Description: For some strange reason, getopt() does not appear to be defined in unistd.h on colonelk when the source is compiled with -D_POSIX_SOURCE. Solution: Inserted some extern's for the missing variables to make the compiler happy. Platforms tested: colonelk, copper Misc. update:
* [svn-r11777] Purpose:Leon Arber2005-12-081-6/+23
| | | | | | | | | | | | | | | | | | | | Feature Description: Added blurb about future todo's for this test. Added support for HDF5_PARAPREFIX to determine the directory where the test file is stored. Solution: Used getenv_all to get the value of HDF5_PARAPREFIX. Note that, if a command-line parameter is passed to the program to specify a path, it will override the value of HDF5_PARAPREFIX. Platforms tested: copper, colonelk Misc. update:
* [svn-r11776] Purpose:Leon Arber2005-12-081-29/+24
| | | | | | | | | | | | | | Added t_posix_compliant to the rest of the build and patched up minor compile bugs/warnings encountered on other platforms. Description: It seems that <getopt.h> needs to be included to get the file to build, even though the man page seems to indicate that <unistd.h> should be sufficient. Solution: Platforms tested: copper, colonelk, sol
* [svn-r11772] Purpose:Leon Arber2005-12-081-0/+847
Feature Description: Added posix compliance tests. Solution: These tests do increasingly complicated sets of writes followed by reads. POSIX standards say that any read that can be proven to occur after a write must include the data in that write. These tests attempt to verify whether the underlying filesystem and i/o layer provide such guarantees. Platforms tested: copper, colonelk, red storm Misc. update: