Skip to content

Conversation

@Joe-Downs
Copy link
Owner

Previously, the PR build tests running on Jenkins were in their own repo - ompi-scripts. This moves them into the main ompi repo and replaces the older, deprecated multi-job Jenkins plugin with the Jenkins Pipeline.

Signed-off-by: Joe Downs joe@dwns.dev
(cherry picked from commit 176d93b)

Previously, the PR build tests running on Jenkins were in their own repo -
ompi-scripts. This moves them into the main ompi repo and replaces the older,
deprecated multi-job Jenkins plugin with the Jenkins Pipeline.

Signed-off-by: Joe Downs <joe@dwns.dev>
(cherry picked from commit babf9ae)
@Joe-Downs Joe-Downs force-pushed the pr/v4.0.x-Jenkinsfile branch from f4e6d0f to d70ae05 Compare January 14, 2023 16:31
@github-actions
Copy link

Hello! The Git Commit Checker CI bot found a few problems with this PR:

a95f43b: Re-enable all Jenkinsfile tests.

  • check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: ecfc4b8

8248e22: Jenkins pr-builder.sh: Add "--bind-to none"

  • check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: b1f3be1

072d308: Jenkinsfile: reduce CI resource using while debugg...

  • check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: 6406e00

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

Similar to
open-mpi/ompi-scripts@7dc912e,
add "--bind-to none" to the mpirun command.

The CI tests on the AWS jenkins instance all run on instances with 1
core.  There's a special case in OMPI to bind to core for a 2 process
run for benchmarking reasons, and this was causing failures in mapping
because there aren't 2 cores on the instance.  So instead turn off
binding for these small tests.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit b1f3be1)
@jsquyres jsquyres force-pushed the pr/v4.0.x-Jenkinsfile branch from a95f43b to 671456c Compare March 21, 2023 20:29
@github-actions
Copy link

Hello! The Git Commit Checker CI bot found a few problems with this PR:

671456c: Jenkins pr-builder.sh: Add "--bind-to none"

  • check_cherry_pick: contains a cherry pick message that refers to a commit that exists, but is in an as-yet unmerged pull request: b1f3be1

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants