-
Notifications
You must be signed in to change notification settings - Fork 835
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 concurrent map writes in executor #2947
Fix concurrent map writes in executor #2947
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
failed to trigger Pull Request pipeline
|
failed to trigger Pull Request pipeline
|
642cd7d
to
1ba34d7
Compare
/test integration |
@RafalSkolasinski I think we need this merged in master first, then I can rebase on top of this - #2954 |
/test notebooks |
1ba34d7
to
01c44be
Compare
/test notebooks |
/test integration |
1 similar comment
/test integration |
01c44be
to
ae5bd4f
Compare
/test integration |
@ivan-valkov: The following test failed, say
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 jenkins-x/lighthouse repository. I understand the commands that are listed here. |
What this PR does / why we need it:
We have a map in the executor package that can be written to concurrently. This leads to
panic
s. To reproduce this on master you can rungo test ./... -count=100
in the executor package. Example output:With this change we don't see this error anymore:
We should check for other possible maps that are written to concurrently and are not protected properly.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
no