4paradigm / 4paradigm/OpenMLDB
sql_cmd_test too easy to fail
Open
bug
storage-engine
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
super unstable
- fails at high frequency
- too much useless log
- failed test affect subsequent tests, hard to debug real test fails
Contributor guide
Research direction
Look for the sql_cmd_test in the test suite. Examine the test logs to identify the high-frequency failures and the excessive logging. Determine how failed tests affect subsequent ones, possibly due to shared state. Focus on isolating tests and reducing log noise to improve stability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100