-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Unnecessary branch updates #761
Comments
Hey @sindrig, thanks for the report. This is weird behavior. I'm not sure why for example this PR is marked as missing reviews: island-is/island.is#5717 Also, looking in the logs, it seems like there were two Kodiak repo workers running at the same time merging 5750 and 5742 |
I'm going to try eliminating those incorrect "missing required reviews" status messages in #762 |
Thanks for the quick response @chdsbd. I did suspect some kind of race condition or error due to parallelism but didn't have anything to go by. When you say two Kodiak repo workers running, you mean there were two runners running in your systems, right? Is there anything we could have spotted? I'll try to keep an eye on pull requests once developers start pushing changes tomorrow and update here if we see this happening still. |
Yeah, I meant two internal workers in Kodiak (actually asyncio tasks) processing the same repo. Kodiak starts repo worker tasks with this code: Lines 519 to 525 in 0c6cda5
I'm honestly not sure yet how it's possible to create two duplicate tasks. 😬 |
We can use reviewDecision to hopefully provide a more consistent view of reviews for a pull request. My theory for some of the issues in #761 is that the GitHub API is being inconsistent when called via the v3 API vs the GraphQL API. Using only reviewDecision will help us avoid depending on the v3 API. I've deployed this change
Pretty sure this is still happening. See this one for example: island-is/island.is@ecefbbf |
Looking in the logs, it seems like the issue of having two workers at the same time isn't happening anymore, but, it seems like I introduced a small bug via e60988d, where if changes are requested, the bot doesn't update the branch correctly. I think this can cause some unnecessary updates. |
I've deployed #765 which should help with some of the unnecessary updates when changes are requested |
Recently we've discovered that kodiak is updating all branches that have
automerge
set, regardless of their place in the queue. The status that's set on the commits is "⛴ merging PR (updating branch)". This causes quite a lot of extra CI jobs, especially when we've got long queues, leading to way longer merge times.merge.message.title
andmerge.priority_merge_label
.Here are some random 3 pull requests:
island-is/island.is#5749
island-is/island.is#5742
island-is/island.is#5721
We can provide more examples or information as needed.
The text was updated successfully, but these errors were encountered: