-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Have a pagination for pr-history #31850
Comments
/sig testing |
For PRs that have a lot of history the pr-history page has a risk of timing out with a 504 error. I.e. https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11054 Increase the CPU limit to raise the chance of the call being successful. Note: kubernetes/test-infra issue created here kubernetes/test-infra#31850 Signed-off-by: Daniel Hiller <dhiller@redhat.com>
For PRs that have a lot of history the pr-history page has a risk of timing out with a 504 error. I.e. https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11054 Increase the CPU limit to raise the chance of the call being successful. Note: kubernetes/test-infra issue created here kubernetes/test-infra#31850 Signed-off-by: Daniel Hiller <dhiller@redhat.com>
GitHub also struggles to render PRs like this ... I'd suggest re-filing the PR |
For PRs that have a lot of history the pr-history page has a risk of timing out with a 504 error. I.e. https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11054 Increase the CPU limit to raise the chance of the call being successful. Note: kubernetes/test-infra issue created here kubernetes/test-infra#31850 Signed-off-by: Daniel Hiller <dhiller@redhat.com>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
If you're still interested in this, please file an issue against https://github.com/kubernetes-sigs/prow/issues, a large effort to split out the prow project was completed. Unfortunately I don't think we have anyone working on prow with the bandwidth for feature requests at the moment but approvers should hopefully review proposed designs/implementations ... |
What would you like to be added:
Have a pagination for pr-history.
Why is this needed:
On PRs with a lot of history requests are timing out with 504 status.
The text was updated successfully, but these errors were encountered: