In the https://github.com/pmix/pmix repo, we have branch protection enabled on all of our branches. On the v1.2 branch, we have 6 CI tests marked as "required". Most of the time this works great. However, every once in a while, we get a PR on that branch that passes all 6 of the CI tests, but GitHub still says "Requests statuses must pass before merging" and doesn't let us merge the PR.
Here's a PR that is currently in this state: https://github.com/pmix/pmix/pull/695. Here's what it looks like:
If you "Show all checks", it shows that all 6 of the required CI tests have passed. These are the same 6 tests listed in https://github.com/pmix/pmix/settings/branches/v1.2.
Are we doing something wrong?
Thanks for being here!
Given that you experience this only occassionally, it doesn't appear that you're doing anything wrong, and in looking at that PR it seems that it was able to be merged some time after you posted this, my suspicion is that it may be a temporary outage situation. Job queues could be getting backed up every once in a while. I'd recommend reaching out to our support team when you see this happen.
If it increases in frequency or you have more questions, our support team can take a closer look at your specific account and repo to do further digging.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
Not sure I understand. The referenced PR has not been merged nor modified since @jsquyres posted this question. We now have multiple PRs on that repo that show the same problem. It is not an intermittent problem - every PR always hits this issue.
Any help would be appreciated. We are holding all our PRs until this can be resolved.
Thanks for the follow up.
On the surface of things, we can't see anything that you're doing wrong. Unfortunately, we don't have access to look into your private account details to see anything underneath the surface. Please contact Support at https://github.com/contact or via email so they can take a deeper look.
I apologize that we don't have anything better to tell you @rhc54. We're constrained in such a way to keep our customers' information secure and private.
It's probably a coincidence, but today, exactly 1 year to date after the initial report, I'm having this exact same issue.