[BUG] mvcc_trx_log_test occasional failed
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.4k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
A clear and concise description of what the bug is.
ref: https://github.com/oceanbase/miniob/actions/runs/10556062499/job/29240856790
[ RUN ] MvccTrxLog.wal_rollback_abnormal
27: /home/runner/work/miniob/miniob/unittest/observer/mvcc_trx_log_test.cpp:711: Failure
27: Expected equality of these values:
27: visible_count
27: Which is: 499
27: insert_num / 2
27: Which is: 500
27: [ FAILED ] MvccTrxLog.wal_rollback_abnormal (31718 ms)
** Environment**
Environment Details sometimes important
- OS Version:
- CPU Arch(x86/arm):
- Compiler:
- Others:
Fast Reproduce Steps(Required)
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Actual Behavior
What is the result? picture is allowed
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with unittest/observer/mvcc_trx_log_test.cpp around line 711 and run the MvccTrxLog.wal_rollback_abnormal test. Investigate why visible_count can be 499 instead of insert_num / 2 and reproduce the intermittent failure in the referenced CI environment. Done means the test no longer fails intermittently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100