Cleanup the configury so we properly check for Singularity under the various typical use-cases
Bring the Singularity support online. We have to turn "off" the sm BTL as it segfaults from inside the container - root cause remains unclear. Also turned "off" the various OPAL shmem components in case they are involved and someone else tries to use them. Happily, the vader BTL works just fine!
Update the configure logic for the new pmix120 component
ckpt
Get the pmix120 component to work - still not really registering or handling notifications, but infrastructure now operates
Cleanup some of the symbol scopes, and provide a more comprehensive rename.h file. Will pretty it up later - let's see how this works
Cleanup the rename files to use the pretty macros
Rename the pmix1xx component to pmix111 so it reflects the actual release it includes
Resolve the problem of PMIx being passed a bogus --with-platform argument when configuring the PMIx tarball code. There is no reason we should be passing --with-platform arguments to any internal subdirectory, so just leave that out when constructing the opal_subdir_args variable.
Update the PMIx code and continue attempting to debug direct modex
Fix a problem in the ORTE PMIx server - there was an early intent to optimize the direct modex by fetching data for all procs from the target job on the remote node, instead of fetching the data one proc at a time. However, this was never completely implemented, and so we would hang if we had multiple overlapping requests for data from more than one proc on the node.
Update PMIx to v1.1.2
Bring Slurm PMI-1 component online
Bring the s2 component online
Little cleanup - let the various PMIx modules set the process name during init, and then just raise it up to the ORTE level. Required as the different PMI environments all pass the jobid in different ways.
Bring the OMPI pubsub/pmi component online
Get comm_spawn working again
Ensure we always provide a cpuset, even if it is NULL
pmix/cray: adjust cray pmix component for pmix
Make changes so cray pmix can work within the integrated
ompi/pmix framework.
Bring singletons back online. Implement the comm_spawn operation using pmix - not tested yet
Cleanup comm_spawn - procs now starting, error in connect_accept
Complete integration
only define the unique fortran symbol depending on
- CAPS
- PLAIN
- SINGLE_UNDERSCORE
- DOUBLE_UNDERSCORE
and bind the f08 symbol to the uniquely defined C symbol.
Use real data structures to make the code simpler.
(perl script written by Jeff)
This gitignore was simply the catenation of all the svn:ignore
properties. However, .gitignore is pretty good at regular expressions
that span the entire tree, so we can consolidate/remove a lot of
redundant entries.
This is a first cut at updating various infrastructure for git. There
will definitely be more commits; some of the scripts require
committed/pushed code (e.g., the various make-tarball scripts). So
it's not possible to know if we got it right without committing/pushing.
The rationale for this name switch is as follows:
0. These two files will be automatically kept up-to-date with
svn:ignore properties in the tree via a cron script. Meaning: if a
developer makes changes to svn:ignore properties, those changes
will automatically be reflected in .gitignore_global /
.hgignore_global within a fixed time period (at the moment,
nightly).
1. Developers who make pure clones of git/hg OMPI repos can copy the
relevant .*ignore_global file to .*ignore. This gives them a good
starting point for a fully-populated ignore file. However, since
the upstream _global file may change over time, developers will
likely want to keep them in sync with their local .*ignore file.
Here's two possibilities:
1a. Maintain a single .*ignore file and manually merge in changes
from the _global file upstream.
1b. Maintain their local ignores in a .*ignore_local file, and
periodically "cat .*ignore_global .*ignore_local > *.ignore"
(e.g., whenever the upstream _global file changes).
2. Developers who make svn+clone checkouts can do similar things as
listed in 1, with the added feature that they cannot make the
mistake of committing their locally-modified .*ignore file back to
SVN (presumably containing references to files that do not exist in
SVN), since the .*ignore file is not in SVN.
Point #2 is probably the stronger of these two reasons -- prevent
mistakes of developers accidentally committing locally-modified
.*ignore files back to SVN.
This commit was SVN r31408.
