test(proxy::config): deflake TestInitialSync#94564
test(proxy::config): deflake TestInitialSync#94564k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
d0394f0 to
b148677
Compare
|
/cc @liggitt |
|
/cc @dcbw |
b148677 to
3e43e62
Compare
|
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
pkg/proxy/config/api_test.go
Outdated
There was a problem hiding this comment.
Do you have any objections to returning the more verbose error with details on the current versus expected not being equal? Is the more concise error suggesting that a timeout would be the only reason this would fail?
There was a problem hiding this comment.
Do you have any objections to returning the more verbose error with details on the current versus expected not being equal
I think we could add some logging if what we got was different from the expected, but it might not be desired to return an error immediately as the poll would be interrupted.
Is the more concise error suggesting that a timeout would be the only reason this would fail?
yes
|
I spotted this flake again https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/97083/pull-kubernetes-bazel-test/1336141738829418496 @dcbw would you mind taking a look? |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
|
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
|
@fejta-bot: Closed this PR. 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. |
|
/remove-lifecycle rotten |
|
@knight42: Reopened this PR. 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. |
|
@knight42: This issue is currently awaiting triage. If a SIG or subproject determines 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/test-infra repository. |
3e43e62 to
aa5563b
Compare
Signed-off-by: Jian Zeng <zengjian.zj@bytedance.com>
aa5563b to
9109d92
Compare
|
/cc @aojea |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, knight42 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 |
|
thank you! |
Signed-off-by: knight42 anonymousknight96@gmail.com
What type of PR is this?
/kind flake
What this PR does / why we need it:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/94556/pull-kubernetes-bazel-test/1302309891905425412
The error could be reproduced by the following patch:
I think the root cause is even after the cache is synced, the execution of event handlers, such as
OnEndpointsAdd, might not have completed yet, so the function inprocessfield received unexpected endpoints.Which issue(s) this PR fixes:
Part of #94528
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: