Only wait for delayed test queue entries if there is no work#1331
Only wait for delayed test queue entries if there is no work#1331k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
The previous solution for processing the work queue sleeps after processing every work item, which isn't ideal for responsive tests, and it was resulting in flakes. Instead, process work as fast as possible, and only sleep when the queue is empty. Note: analysis of the failing logs and the possible fix was assisted by an "AI" agent. Signed-off-by: Nolan Brubaker <nolan@nbrubaker.com> Co-Authored-By: Claude Code <noreply@anthropic.com>
|
This issue is currently awaiting triage. If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the The DetailsInstructions 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. |
|
/test pull-cloud-provider-aws-test Running again to get more data points for flakes |
|
/assign @kmala |
|
/assign @elmiko @JoelSpeed |
|
/test pull-cloud-provider-aws-test |
|
/test pull-cloud-provider-aws-e2e-kubetest2 |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kmala 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 |
What type of PR is this?
/kind flake
What this PR does / why we need it:
CI has been unreliable, reporting failures with the tagging controller tests on unrelated changes.
This is because the previous solution for processing the work queue sleeps after processing every work item, which isn't ideal for responsive tests, and it was resulting in flakes.
Instead, process work as fast as possible, and only sleep when the queue is empty.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
The logs for these flakes were analyzed with the help of an AI agent.
Does this PR introduce a user-facing change?: