Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Fix a bug in the cherry pick checker #8947

Merged
merged 1 commit into from
May 11, 2021

Conversation

StevenGood154
Copy link
Contributor

The check_cherry_pick() function in .github/workflows/git-commit-checks.py
would incorrectly allow some cherry-pick messages reffering to commits that
do not exist in the base repository, specifially when the commit exists only
on a pull request that has not been merged. This has been resolved; the
workflow will exit with a failure unless the referenced commit exists in
the base repository.

Note that this approach only works because all commits are introduced to
the open-mpi/ompi through pull requests from forks.

Signed-off-by: Steven Good [email protected]
Signed-off-by: Brett Wiseman [email protected]
Signed-off-by: Christine Van Kirk [email protected]

The check_cherry_pick() function in .github/workflows/git-commit-checks.py
would incorrectly allow some cherry-pick messages reffering to commits that
do not exist in the base repository, specifially when the commit exists only
on a pull request that has not been merged. This has been resolved; the
workflow will exit with a failure unless the referenced commit exists in
the base repository.

Note that this approach only works because all commits are introduced to
the open-mpi/ompi through pull requests from forks.

Signed-off-by: Steven Good <[email protected]>
Signed-off-by: Brett Wiseman <[email protected]>
Signed-off-by: Christine Van Kirk <[email protected]>
@ompiteam-bot
Copy link

Can one of the admins verify this patch?

@jsquyres jsquyres self-requested a review May 11, 2021 00:41
Copy link
Member

@jsquyres jsquyres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Can you test cherry-picking this to the v4.1.x branch? It should fail the CI test before we merge this PR here on master.

@jsquyres
Copy link
Member

ok to test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants