We’ve been having an issue on and off for a while now that looks extremely similar to the issues others have been reporting, where CI jobs never complete successfully for Github PRs. However, only just now I noticed one key difference.
Unlike what others have been reporting, when our PR checks won’t complete, it turns out it’s because there are TWO “Travis CI - Pull Request” checks listed for the same PR. They’re also both listed in the Checks tab as separate Github Actions. I thought one of the two was a Branch build, but only today realized they’re both Pull Request builds.
What’s weirder, they’re both THE SAME BUILD. Both jobs are showing status for the exact same TravisCI Build job, listed by the same number, but showing different status. If I click through to Travis-ci.com from either one, I land on the same status page there (showing a successful build).
It looks like, because they’re both pointing at the same Travis job, only one of the two checks ever receives the build status update from Travis, and the other one will remain in limbo forever.
Here’s an example of a PR currently in that state. It’s not urgent, so I can leave it there for a bit.
Experience tells me that if I were to push a commit, even an empty one, onto that PR branch, that would un-stick the build. The second “phantom” PR check would vanish, and the other one would complete successfully.
But nothing else seems to correct this, including restarting the Travis job — that would only cause both checks to go back into “Queued — Build Created” state, and once again only one of them would make it back out to “Successful”.
As far as I know we have everything configured correctly. We’ve switched over to the GitHub Actions integration, we’re using travis-ci.com, etc. We were encouraged to upgrade our config after having more-typical issues with builds on travis-ci.org.
What could be causing those duplicate PR build entries?