Bump the limit of rehearsed jobs #4789
Conversation
We are not rehearsing any jobs for repositories with many presubmits, which is the opposite of what we want to be doing. In general we should not worry about starting a thundering herd if all jobs belong to one configuration, as any new pull request to the same repository will trigger the same set of jobs normally. Signed-off-by: Steve Kuznetsov <[email protected]>
openshift-ci-robot
added
the
size/XS
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stevekuznetsov The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
@stevekuznetsov: Updated the
DetailsIn response to this:
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. |
Folks have been tuning this since b0d60e3 (Bump the limit of rehearsed jobs, 2019-08-19, openshift#4789), most recently in 3f0040e (Raise rehearsal-limit to 45 temporarily, 2020-02-03, openshift#6999). But with [1], we no longer need to fuss with this setting in order to see rehearsals for changes that touch lots of jobs, so let it fall back to pj-rehearse's default of 15. [1]: openshift/ci-tools#1315
3 participants
We are not rehearsing any jobs for repositories with many presubmits,
which is the opposite of what we want to be doing. In general we should
not worry about starting a thundering herd if all jobs belong to one
configuration, as any new pull request to the same repository will
trigger the same set of jobs normally.
Signed-off-by: Steve Kuznetsov [email protected]