Skip to content
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

TestReconcileInboundNATRule test cases can not be run in parallel #2919

Open
jackfrancis opened this issue Dec 8, 2022 · 6 comments
Open
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@jackfrancis
Copy link
Contributor

/kind bug

[Before submitting an issue, have you checked the Troubleshooting Guide?]

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

@mboersma determined in #2646 that the cases in the TestReconcileInboundNATRule unit test trigger the race detector. This could be an innocuous outcome of the way those tests are setup, or it could be that refactoring the tests to enable parallel cases to run is not worth the effort; or it could mean that there is actually something worrisome happening under the hood.

Let's investigate and rule out anything worrisome.

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • cluster-api-provider-azure version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@jackfrancis jackfrancis added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Dec 8, 2022
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 8, 2022
@ShivamTyagi12345
Copy link
Member

ShivamTyagi12345 commented Dec 12, 2022

Is this issue fixed with PR #2646 ? If not! May i take this up? @jackfrancis

/ assign

@mboersma
Copy link
Contributor

In #2646 we just commented out t.Parallel() to fix the problem. Maybe that's fine, but maybe there's something in the test itself that could be changed to allow the t.Parallel() line to be restored and have go test -race still work.

Thanks for taking a look!

/assign @ShivamTyagi12345

@ShivamTyagi12345
Copy link
Member

Started with this issue. Apologies for the delay due to Exams, and thanks for your reply

@willie-yao
Copy link
Contributor

willie-yao commented Mar 6, 2023

Hi @ShivamTyagi12345, thanks for taking a look at this issue! Are you still working on this as of now?

@sonasingh46 sonasingh46 added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Aug 3, 2023
@dtzar
Copy link
Contributor

dtzar commented Aug 3, 2023

@ShivamTyagi12345 are you still working on this?

@mboersma
Copy link
Contributor

/unassign @ShivamTyagi12345

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
Status: Todo
Development

No branches or pull requests

7 participants