-
Notifications
You must be signed in to change notification settings - Fork 58
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
e2e flake: fatal error: concurrent map read and map write #1571
Comments
nirs
added a commit
to nirs/ramen
that referenced
this issue
Oct 21, 2024
We modify the textcontext map form multiple tests running in parallel, so we must synchronize access to the map. Fixes RamenDR#1571 Signed-off-by: Nir Soffer <[email protected]>
nirs
added a commit
to nirs/ramen
that referenced
this issue
Oct 22, 2024
We had 2 places using a test context - test suites, and action helpers. To work with both, we store the test context in a map and had complicated search mechanism to locate the context in both the parent and child sub-tests. This failed randomly since the map was not protected with a mutex. Simplify the design by implementing the actions (deploy, enable, ..) in the test context. With this we can create a test context instance and pass it to the code running a test flow, and we don't need to manage any global state. Fixes: RamenDR#1571 Signed-off-by: Nir Soffer <[email protected]>
nirs
added a commit
to nirs/ramen
that referenced
this issue
Oct 22, 2024
We had 2 places using a test context - test suites, and action helpers. To work with both, we store the test context in a map and had complicated search mechanism to locate the context in both the parent and child sub-tests. This failed randomly since the map was not protected with a mutex. Simplify the design by implementing the actions (deploy, enable, ..) in the test context. With this we can create a test context instance and pass it to the code running a test flow, and we don't need to manage any global state. Fixes: RamenDR#1571 Signed-off-by: Nir Soffer <[email protected]>
nirs
added a commit
to nirs/ramen
that referenced
this issue
Oct 30, 2024
We had 2 places using a test context - test suites, and action helpers. To work with both, we store the test context in a map and had complicated search mechanism to locate the context in both the parent and child sub-tests. This failed randomly since the map was not protected with a mutex. Simplify the design by implementing the actions (deploy, enable, ..) in the test context. With this we can create a test context instance and pass it to the code running a test flow, and we don't need to manage any global state. Fixes: RamenDR#1571 Signed-off-by: Nir Soffer <[email protected]>
ShyamsundarR
pushed a commit
that referenced
this issue
Oct 31, 2024
We modify the textcontext map form multiple tests running in parallel, so we must synchronize access to the map. Fixes #1571 Signed-off-by: Nir Soffer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like a random failure - maybe we are missing locking on a map?
Build: https://github.com/RamenDR/ramen/actions/runs/10992671688/job/30522993349
The text was updated successfully, but these errors were encountered: