Thread Safety test for UpdateSubsSyncCounterStorage (#2918)#438
Conversation
Introduces a test that ensure that the UpdateSubsSyncCounterStorage function is thread safe and avoids concurrent map writes. Signed-off-by: Alexander Greene <greene.al1991@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 84ab8d27288ae40d92bdf7f58ebec537f8b187fc
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene 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 |
|
/lgtm |
|
/retest |
|
This is just a unit test backport, so I'm gonna save the qe/px/docs team some time. |
|
/test e2e-gcp-ovn |
|
/retest |
|
/retest |
|
/retest |
|
/retest |
1 similar comment
|
/retest |
|
@awgreene: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
…penshift#438) Signed-off-by: grokspawn <jordan@nimblewidget.com> Upstream-repository: api Upstream-commit: d6a691fa17280bfc5f17e22e73edb6fcd0b64503
Introduces a test that ensure that the UpdateSubsSyncCounterStorage function is thread safe and avoids concurrent map writes.
Signed-off-by: Alexander Greene greene.al1991@gmail.com
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 84ab8d27288ae40d92bdf7f58ebec537f8b187fc