test: deflake TestBackoffRetryCount

[Camila-B]

• This updates TestBackoffRetryCount so that it uses a timeout of 1 second instead of the reimport count when calling the Run function

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tiffanny29631 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[google-oss-prow]

Hi @Camila-B. Thanks for your PR.

I'm waiting for a GoogleContainerTools member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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

[karlkfi]

/ok-to-test

[karlkfi]

This looks potentially less flaky, but still not deterministic. If the machine is busy it could start the timer and then pause the thread for more than a second before continuing. This is common on CI clusters with many jobs running in parallel.

Is there a way we can refactor the test to test it in a way that's not time based? One option would be to inject named timer factories instead of named timeouts.