Removed deadlock in find dynamic region

.ci/README.md

@@ -0,0 +1,16 @@
+# Open MPI Continuous Integration (CI) Services
+## Mellanox Open MPI CI
+### Scope
+[Mellanox](https://www.mellanox.com/) Open MPI CI is intended to verify Open MPI with recent Mellanox SW components ([Mellanox OFED](https://www.mellanox.com/page/products_dyn?product_family=26), [UCX](https://www.mellanox.com/page/products_dyn?product_family=281&mtag=ucx) and other [HPC-X](https://www.mellanox.com/page/products_dyn?product_family=189&mtag=hpc-x) components) in the Mellanox lab environment.
+
+CI is managed by [Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops) service.
+
+Mellanox Open MPI CI includes:
+* Open MPI building with internal stable engineering versions of UCX and HCOLL. The building is run in Docker-based environment.
+* Sanity functional testing.
+### How to Run CI
+Mellanox Open MPI CI is triggered upon the following events:
+* Create a pull request (PR). CI status is visible in the PR status. CI is restarted automatically upon each new commit within the PR. CI status and log files are also available on the Azure DevOps server.
+* Trigger CI with special PR comments (for example, `/azp run`). Comment triggers are available only if the comment author has write permission to the PR target repo. Detailed information about comment triggers is available in the official Azure DevOps [documentation](https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#comment-triggers).
+### Support
+In case of any issues, questions or suggestions please contact to [Mellanox Open MPI CI support team](mailto:[email protected]).

.ci/mellanox/azure-pipelines.yml

@@ -0,0 +1,47 @@
+trigger: none
+pr:
+  - main
+  - v*.*.x
+
+pool:
+  name: Default
+  demands:
+  - AGENT_CI_TARGET -equals ompi
+  - MLNX_IB_DEVICE -equals yes
+
+variables:
+  ompi_jenkins_scripts_git_repo_url: https://github.com/mellanox-hpc/jenkins_scripts.git
+  ompi_jenkins_scripts_git_branch: ompi_v4.0.x
+  # Enable debug information, supported values: true, false
+  debug: true
+
+jobs:
+- job: mellanox_ompi_ci
+  displayName: Mellanox Open MPI CI
+  timeoutInMinutes: 240
+  container:
+    image: rdmz-harbor.rdmz.labs.mlnx/hpcx/ompi_ci:latest
+    options: -v /hpc/local:/hpc/local -v /opt:/opt --uts=host --ipc=host --ulimit stack=67108864
+      --ulimit memlock=-1 --security-opt seccomp=unconfined --cap-add=SYS_ADMIN --device=/dev/infiniband/
+  steps:
+  - task: DeleteFiles@1
+    displayName: Cleanup workspace folder
+    inputs:
+      sourceFolder: $(Pipeline.Workspace)
+      contents: |
+        **/jenkins_scripts
+  - checkout: self
+    submodules: true
+    path: ompi
+    clean: true
+  - bash: |
+      set -eE
+      [ "$(debug)" = "true" ] && set -x
+      cd $(Pipeline.Workspace)
+      git clone $(ompi_jenkins_scripts_git_repo_url)
+      cd $(Pipeline.Workspace)/jenkins_scripts && git checkout $(ompi_jenkins_scripts_git_branch)
+      export WORKSPACE=$(Pipeline.Workspace)/ompi
+      # TODO: rework ompi_test.sh to avoid Jenkins mentions
+      export JENKINS_RUN_TESTS=yes
+      $(Pipeline.Workspace)/jenkins_scripts/jenkins/ompi/ompi_test.sh
+    displayName: Build and test Open MPI

.github/workflows/README.md

@@ -0,0 +1,7 @@
+Be aware that changes to the contents of these files will affect the
+Pull Request in which you make the changes!
+
+For example, if you create a PR that changes one of the Github Actions
+in this directory, it will be used in the CI *for that PR*.
+
+You have been warned.  :smile:

.github/workflows/git-commit-checks.json

@@ -0,0 +1,3 @@
+{
+    "cherry pick required" : 1
+}