MDEV-37862 - innodb.gap_locks test failure: 0 lock structs, 0 row locks #4511
+3
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
Member
|
Sergey Vojtovich ***@***.***> writes:
@svoj requested your review on: MariaDB/server#4511 MDEV-37862 -
innodb.gap_locks test failure: 0 lock structs, 0 row locks.
I cannot push this to 10.6 for you, because trying to push one fix for
sporadic gets blocked by github due to the failure of another sporaric, and
I was refused the access to machines I need to debug the second failure.
- Kristian.
|
Test was affected by incompletely closed preceding connections. Make test agnostic to concurrent connections by querying InnoDB status only for connections that it uses. This is an addition to 3b2169f, which didn't handle a case when preceding test has active transaction on disconnect.
svoj
force-pushed
the
pr-10.6-MDEV-37862
branch
from
e21058b to
8a6bb95
Compare
Contributor
Author
|
@knielsen should be mergeable now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test was affected by incompletely closed preceding connections.
Make test agnostic to concurrent connections by querying InnoDB status only for connections that it uses.
This is an addition to 3b2169f, which didn't handle a case when preceding test has active transaction on disconnect.