-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix data race in TestPriorityQueue_AssignedPodAdded #73022
fix data race in TestPriorityQueue_AssignedPodAdded #73022
Conversation
Hi @denkensk. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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/test-infra repository. |
/ok-to-test |
/priority important-soon |
@@ -95,6 95,18 @@ var highPriorityPod, highPriNominatedPod, medPriorityPod, unschedulablePod = v1. | |||
}, | |||
} | |||
|
|||
func addOrUpdateUnschedulableQ(p *PriorityQueue, pod *v1.Pod) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/addOrUpdateUnschedulableQ/addOrUpdateUnschedulablePod/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done thank you
p.unschedulableQ.addOrUpdate(pod) | ||
} | ||
|
||
func getUnschedulableQ(p *PriorityQueue, pod *v1.Pod) *v1.Pod { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/getUnschedulableQ/getUnschedulablePod/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done thank you
2986d89
to
28e6bbc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
@denkensk, thanks for fixing the the data race test.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bsalamat, denkensk 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:
Approvers can indicate their approval by writing |
/kind bug |
What type of PR is this?
What this PR does / why we need it:
I'm very sorry about that. This problem did not occur in the ci of code merged, but in another ci.
UnschedulablePodsMap is not thread-safe. In scheduling_queue.go, lock will be acquired before operating UnschedulablePodsMap. But in scheduling_queue_test.go, lock isn‘t be acquired. In the previous case, only a single thread runs so it's ok. But after add goroutine flushUnschedulableQLeftover, there will be data race. So I need to acquire lock before operating UnschedulablePodsMap.
Which issue(s) this PR fixes:
Fixes #73021
Special notes for your reviewer: