sig-proxy test: bump timeout

[vrothberg]

Bump the timeout waiting for the container to process the signal. The comparatively short timeout is most likely responsible for flakes in gating tests.

Fixes: #16091
Signed-off-by: Valentin Rothberg [email protected]

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrothberg

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 [vrothberg]

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

[edsantiago]

I don't think of five seconds as a "short timeout" for handling a signal... but, shrug, LGTM if there's no other option.

[vrothberg]

@edsantiago wasn't it 2.5 seconds of timeout before and now we're at 5? Some other timeouts are at 10.

[edsantiago]

Ugh, good point: $timeout is in half-seconds; I missed that.

The thing that bothers me is that this is a new test dating to Sept 20 (#15131). And it relies on podman logs, which is known to be unreliable (#16132, which, granted, is podman-remote). I'm OK with bumping this timeout, but I will keep a close eye on future flakes here.

[rhatdan]

/lgtm
/hold

[edsantiago]

/hold cancel

[vrothberg]

I'm OK with bumping this timeout, but I will keep a close eye on future flakes here.

Thanks for keeping an eye on these flakes! Bumping timeouts never gives me a satisfying feeling (or accomplishment) but that is the best "guess" I have for this flake.

[lsm5]

/cherrypick v4.3

[openshift-cherrypick-robot]

@lsm5: new pull request created: #16516

In response to this:

/cherrypick v4.3

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.