Skip to content

Very few PRs are merging #92937

@spiffxp

Description

@spiffxp

I opted to open a new issue instead of re-opening #90647

The tide pool for kubernetes/kubernetes master is much larger than usual. Put another way, a lot of PRs are eligible for merge, but they're not getting merged. This is due to batches of PRs failing tide's retest-prior-to-merge step.

Screen Shot 2020-07-09 at 8 32 47 AM
(taken from: https://monitoring.prow.k8s.io/d/d69a91f76d8110d3e72885ee5ce8038e/tide-dashboard?orgId=1&from=now-30d&to=now)

Some of this is likely due to a rush to land PRs before today's Code Freeze deadline (ref: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.19#tldr)

Some useful links for troubleshooting

Some links for context / prior discussion

/priority critical-urgent
/sig release
/sig testing
/milestone v1.19

FYI @kubernetes/ci-signal @kubernetes/release-team

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/releaseCategorizes an issue or PR as relevant to SIG Release.sig/testingCategorizes an issue or PR as relevant to SIG Testing.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions