-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[docdb] QLTabletTest.OperationMemTracking is flaky #3254
Labels
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
priority/medium
Medium priority issue
Comments
bmatican
added
kind/failing-test
Tests and testing infra
area/docdb
YugabyteDB core features
labels
Jan 6, 2020
bmatican
added a commit
that referenced
this issue
Jan 13, 2020
Summary: Test was changing the value while background threads were potentially accessing it. Test Plan: `ybd tsan --cxx-test client_ql-tablet-test --gtest_filter QLTabletTest.OperationMemTracking -n 500 --tp 4` Reviewers: sergei, mikhail Reviewed By: mikhail Subscribers: ybase Differential Revision: https://phabricator.dev.yugabyte.com/D7760
Found another race due to an unprotected, not atomic write from the test
|
yugabyte-ci
added
kind/bug
This issue is a bug
priority/medium
Medium priority issue
labels
Jun 8, 2022
This was referenced Sep 8, 2022
This was referenced Nov 27, 2023
This was referenced Nov 30, 2023
This was referenced Dec 20, 2023
This was referenced May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
priority/medium
Medium priority issue
Jira Link: DB-1608
Started off trying to fix a TSAN race:
After that though, test is still flaky. Down to 13/500 failures with
Current set of errors seen:
7 times
4 times
1 time
1 time
The text was updated successfully, but these errors were encountered: