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

deployments: fix data races #14121

Merged
merged 2 commits into from
Aug 16, 2022
Merged

deployments: fix data races #14121

merged 2 commits into from
Aug 16, 2022

Conversation

schmichael
Copy link
Member

Part 3/n of my effort to make agent tests race free. (Prev: #14120)

Both priority and state related fields may be mutated concurrently and need to be accessed with the lock acquired.

Our whole approach to flush()/setenabled in these daemon goroutines could be refactored to avoid these locking concerns (eg creating whole new structs instead of re-initializing all fields on "live" structs), but it was out of scope for my refactoring effort.

Both priority and state related fields may be mutated concurrently and
need to be accessed with the lock acquired.
Copy link
Member

@jrasell jrasell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a minor comment about variable name collision.

nomad/deploymentwatcher/deployments_watcher.go Outdated Show resolved Hide resolved
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants