Picked up the relevant parts of [2bda6bc7], [49b74176] and [59cbc846].

No reviewer.

No reviewer.

If data sieving is not supported by the underlying file system (e.g. PVFS,
PLFS, BGLOCKLESS) then there is no reason to turn write-only requests
into read-write requests.  Suggestion first reported by David Knaak of Cray.

Reviewed-by: David Knaak <knaak@cray.com>

Kenneth Raffenetti authored Sep 18, 2013 and Pavan Balaji committed Sep 18, 2013

FreeBSD does not support this attribute. Including this runtime
test ensures nemesis will not override the allocate_shm function
pointer unless it is supported. Fixes #1926

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

- large_type now conforms to mpich test guidelines.
- additional datatype cases that do not rely on "large MPI_Aint" (but
  32 bit platforms probably still cannot process these types)

Fixup the f90tof77 failcheck patch to eliminate a stray blank

Add a test for success in the executions of the f77tof90 script in autogen.sh

Signed-off-by: Antonio J. Pena <apenya@mcs.anl.gov>

RobL wears the "bad commit of shame" badge for missing these in the last
commit

An complimentary test to large_count.  Whereas large_count hits an
assertion early on about size being negative, this test progresses
further into the dataloop code... where it asserts about a count of
blocks being negative:

Assertion failed in file ../src/mpid/common/datatype/dataloop/segment_count.c at line 100: *blocks_p > 0

refer to ticket #1893

RobL's large-count/large-type combo branch will address this once it
lands.

Initialized a variable in mpi_t_str.c to a garbage value so that the test will
more easily trigger MPI_T implementation bugs.

Current MPI_T implementation is incorrect, so I also added the test to xfail.

One was discovered on reading the code; the correct test for the enum
case was not made.  The second was discovered by the Blue Waters team when
testing the most recent Cray MPI release.  Its not clear how this passed our
tests.

The MPI_Errhandler callback function is defined as the MPI Standard as having
a valist which is implementation specific. This adds a specification for those
parameters to the user doc and the man page for MPI_Comm_create_errhandler.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

As of MPI-2, MPI_Init will accept NULL as input parameters. This wasn't
mentioned in the man page though this is pertinent information.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Wesley Bland authored Aug 23, 2013 and Pavan Balaji committed Aug 23, 2013

We don't provide support for Windows anymore. There shouldn't be
instructions for installing and using it in the install guide.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Wesley Bland authored Aug 21, 2013 and Pavan Balaji committed Aug 23, 2013

We don't provide support for Windows anymore. There shouldn't be instructions
for installing and using it in the user guide.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

The default "aggregators per peset" value of 8 had not been changed
since Blue Gene /L.  Further, allow one to set the environment variable
BGMPIO_NAGG_PSET to have the same effect as setting the "bg_nodes_pset"
hint.  Since this is all very confusing on /Q, toss in a few more (but
no doubt not enough) comments.

Reviewed-by: Bob Cernohous <bobc@us.ibm.com>

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

Use _exit instead of kill to more reliably fail processes in
fault tolerance tests. _exit ends a process immediately rather than
relying on kill/sleep combo. Also, tests now output " No Errors"
correctly upon success.

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

We were listing some of the configure options in the README.
Unfortunately, these are not consistent with the configure file since
they are not autogenerated.  Fixes #1921.

Signed-off-by: Antonio J. Pena <apenya@mcs.anl.gov>

Signed-off-by: Antonio J. Pena <apenya@mcs.anl.gov>

sizeof() is used inconsistently in pm/hydra/utils/sock/sock.c. In some
places this is size of type, in some - size of variable.

Thanks to Yauheni Zelenko for reporting this error.

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

Pavan Balaji authored Aug 14, 2013 and Kenneth Raffenetti committed Aug 14, 2013

We need to make sure that the xfail tickets that are added to the test
list are not left in there permanently.  This script checks whether
these tickets are still open and points out of they are not, but the
xfail is still listed.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Pavan Balaji authored Aug 13, 2013 and Kenneth Raffenetti committed Aug 14, 2013

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

FreeBSD 9.1-RELEASE has aio routines that appear to work but
when called return ENOSYS.  We can handle that, though, if we
check for that condition.

Yet more error handling routines added to another I/O test that does not check errors.

freebsd did not like this expr syntax for some reason. Since we require
autoconf-2.67 or newer, let's use AS_VAR_ARITH and make portable shell scripts
autoconf's problem

This reverts commit 4614eb44.

The environment description did not mention what the port range 0:0
meant.

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

The genparams script was displaying the range format as {low,high},
while the format the environment variables accept is low:high.  This
commit fixes the script to display the default in the correct format.

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

We might add some MPIX functions to the interface (for active
messages), but those are not a part of the libmpich ABI.  This value
needs to be verified when we are making the actual release.

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

Xin Zhao authored Aug 08, 2013 and Pavan Balaji committed Aug 08, 2013

Initialize "list_complete" before entering MPIDI_CH3I_RMAListPartialComplete
because it is used in that function.

Fixes ticket #1906.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

The error message in MPID_nem_tcp_bind line 580 was incorrectly reporting the
port that was being attempted due to incrementing the variable at the end of
the for loop and not accounting for that in the error message. This patch
subtracts one if the port was not succesfully bound when printing out the
value for the error message.

Thanks to Yauheni Zelenko for reporting this error.

Signed-off-by: Huiwei Lu <huiweilu@mcs.anl.gov>

Michael Blocksome authored Aug 08, 2013 and Pavan Balaji committed Aug 08, 2013

There are three configure options and two install cases that need to be
handled.

The configure could have be done on a bgq system that has V1R2M1+
installed or on a bgq system that has a pre-V1R2M1 installation. In
V1R2M1 the location and names of the pami libraries changed.

The three configure options are:
  --with-bgq-install-dir ..... forces use of a specific bgq install
  --with-pami[-include|-lib] . forces use of a specific pami install
  PAMILIBNAME ................ forces use of a specific pami library name

Signed-off-by: Bob Cernohous <bobc@us.ibm.com>
Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Increase the number of RMA operations issued within the epoch.  The
error seems to happen rarely, so increasing the number of RMA
operations increases the probability of it occurring.

Signed-off-by: Xin Zhao <xinzhao3@illinois.edu>