🐛 Bump timeout for CI peribolos to 4h

[cardil]

Changes

• 🐛 Bump timeout for CI peribolos to 4h

Context

Should fix issues like https://prow.knative.dev/view/gs/knative-prow/logs/ci-knative-extensions-peribolos/1929946357959757824

Which issue(s) this PR fixes:

Related to #662
Follow up on #665

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cardil

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:

• OWNERS [cardil]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cardil]

/assign @dsimansk

[evankanderson]

It looks like our GitHub API calls are taking 10+ seconds over the 2 hour window. Do we know why the latency is so high.

Approving for now, but I'm slightly concerned about the duration.

/lgtm

[knative-prow]

@cardil: Updated the job-config configmap in namespace default at cluster default using the following files:

• key peribolos.yaml using file prow/jobs/custom/peribolos.yaml

In response to this:

Changes

• 🐛 Bump timeout for CI peribolos to 4h

Context

Should fix issues like https://prow.knative.dev/view/gs/knative-prow/logs/ci-knative-extensions-peribolos/1929946357959757824

Which issue(s) this PR fixes:

Related to #662
Follow up on #665

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-sigs/prow repository.

[dsimansk]

It looks like our GitHub API calls are taking 10+ seconds over the 2 hour window. Do we know why the latency is so high.

Approving for now, but I'm slightly concerned about the duration.

/lgtm
A bit of context is here: https://cloud-native.slack.com/archives/C04LY4M2G49/p1748886167174489

We've been running into "secondary limits" per #662.

So far we dropped those a few times:

1. From former hourly 2000, burst 1000 - job failed in a couple of minutes
2. To 1000, 500 - job failed within 30 min
3. To prow's default 300, 100 - it can succeed with enough time

I agree, it takes too long to complete. In case of knative org the duration is around 1 hour. But knative-extensions was closing to 2h mark, intermittently surpassing and getting terminated. I think --fix-team-repos is causing the issue, posting too many mutating requests that are "priced" higher that get queries etc. The job usually failed during execution of RemoveTeamRepoBySlug as it goes through a list of teams and applying the change on every repo, resulting in too many permutations.