-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Fix single override creates many ProwJobs in the system #24447
Conversation
Hi @jmguzik. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
/ok-to-test |
This commit addresses the problem described in kubernetes#22690. Override once issued, can spawn many the almost same prowjobs. The root cause of the problem takes the origin in the statuses returned by GitHub API. There are multiple statuses with the same context which reflects the history of the job. One repetition of context handling for override is enough, rest of the statuses can be ignored. This commit also adjusts unit tests to the real situation, removing maps as overlapping statuses are possible. Signed-off-by: Jakub Guzik <jguzik@redhat.com>
/hold cancel |
/assign @fejta |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fejta, jmguzik, petr-muller The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This commit addresses the problem described in #22690. Override once issued,
can spawn many the almost same prowjobs. The root cause of the problem takes
the origin in the statuses returned by GitHub API. There are multiple statuses
with the same context which reflects the history of the job. One repetition of
context handling for override is enough, rest of the statuses can be ignored.
This commit also adjusts unit tests to the real situation, removing maps as
overlapping statuses are possible.
/fixes #22690
Signed-off-by: Jakub Guzik jguzik@redhat.com