CI Bots Information Page - openpmix/openpmix GitHub Wiki
All PRs are tested before they can be merged. Sometimes it is necessary to 're-trigger' CI testing on a PR due to, for example, a network issue. To re-trigger a specific CI test or group of CI tests add a comment to your PR with one of the following strings (prefixed with bot:
). The CI bots watch the comments and look for these strings to trigger testing. Some testing might be delayed due to the load on the CI servers.
- Trigger a GitHub Action: See This Page
- Trigger all CI:
bot:retest
- Trigger all Mellanox CI:
bot:mellanox:retest
- Trigger all IBM CI:
bot:ibm:retest
(see section below for fine tuning) - Trigger LANL CI:
bot:lanl:retest
GitHub Action CI Tests
Cross Version Triggers
The cross-version tests are run using a docker container. The source for that container is maintained here and the container is hosted on Docker Hub. Instructions are provided to help you reproduce any errors.
- To trigger a GitHub Action: See This Page
IBM CI Triggers
bot:ibm:retest
: Basic testing- Triggers a parallel build with the following configurations:
- GNU Compiler on 5 nodes (adjustable via
bot:ibm:nodes:#:test
) - XL Compiler on 3 nodes
- PGI Compiler on 3 nodes
- GNU Compiler on 5 nodes (adjustable via
- Triggers a parallel build with the following configurations:
bot:ibm:nodes:#:test
: Increase the number of nodes used for GNU Compiler test- Must also specify
bot:ibm:retest
- Default:
5
nodes - Minmum:
1
node - Maximum:
128
nodes
- Must also specify
bot:ibm:ppn:#:test
: Define the number of processes-per-node to use during testing- Must also specify
bot:ibm:retest
- Default:
4
- Minmum:
1
- Maximum:
20
- Must also specify