fix pusher concurrent close channel#7473
Conversation
|
Hi @lengrongfu. Thanks for your PR. I'm waiting for a containerd 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. 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. |
7b9e3b6 to
0791663
Compare
da3da4e to
7318653
Compare
Signed-off-by: rongfu.leng <[email protected]>
7318653 to
63a7d8a
Compare
|
@akhilerm please take a look. |
akhilerm
left a comment
There was a problem hiding this comment.
@lengrongfu have a question on the change in the test. The change in Close() looks good.
|
@dcantah Hi,can you help review this PR? thanks! |
|
/ok-to-test |
|
@lengrongfu: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
|
/ok-to-test |
|
@samuelkarp k8s jobs are ✅ |
|
I think this should be cherry-picked to 1.6 and 1.5 |
|
Perfect! I'm not going to have time tomorrow so thanks a bunch |
|
cherry-picked this PR to #7479 |
goroutine1:
containerd/remotes/docker/pusher.go
Line 290 in 8abee9c
goroutine2:
containerd/remotes/docker/pusher_test.go
Line 152 in 8abee9c
Use
sync.Onceto ensure thatclose(pw.pipeC)is executed only once.issue: #7471