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

Fix global read-write lock handling when not declared on top level #4039

Merged
merged 5 commits into from
Oct 3, 2024

Conversation

marcphilipp
Copy link
Member

@marcphilipp marcphilipp commented Oct 2, 2024

Overview

Prior to this change additional locks were not cleared from siblings
when discovering the global read-write lock on a test descriptor which
led to incompatible locks and caused test execution to fail.

Fixes #4027.


I hereby agree to the terms of the JUnit Contributor License Agreement.


Definition of Done

Prior to this change additional locks were not cleared from siblings
when discovering the global read-write lock on a test descriptor which
led to incompatible locks and caused test execution to fail.

Fixes #4027.
@marcphilipp marcphilipp force-pushed the marc/4027-fix-global-lock-coarsening branch from ea17b28 to 5bab0e4 Compare October 2, 2024 11:23
@marcphilipp marcphilipp marked this pull request as ready for review October 2, 2024 11:24
@marcphilipp marcphilipp requested a review from leonard84 October 2, 2024 11:24
@marcphilipp marcphilipp merged commit 871e800 into main Oct 3, 2024
15 checks passed
@marcphilipp marcphilipp deleted the marc/4027-fix-global-lock-coarsening branch October 3, 2024 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Declaring the global read-write lock on a leaf node should not fail execution
3 participants