slow test `TestIndexMergePanic` in `pkg/executor/test/indexmergereadtest` pkg
- Dominant language
- Go
- Stars
- 40.6k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Bug Report
Average timecost was 144056.0000ms between TIMESTAMP("2024-01-08") AND TIMESTAMP("2024-01-30")
Found records: 5 (filter only for runs that timecost >= threshold)
Max timecost: 146590ms
Min timecost: 142080ms
Avg timecost: 144056.0000ms
- [CI build](https://do.pingcap.net/jenkins/job/pingcap/job/tidb/job/ghpr_unit_test/2544/): used 144720ms
- [CI build](https://do.pingcap.net/jenkins/job/pingcap/job/tidb/job/ghpr_unit_test/2514/): used 142080ms
- [CI build](https://do.pingcap.net/jenkins/job/pingcap/job/tidb/job/ghpr_unit_test/2082/): used 142840ms
- [CI build](https://do.pingcap.net/jenkins/job/pingcap/job/tidb/job/ghpr_unit_test/2012/): used 144050ms
- [CI build](https://do.pingcap.net/jenkins/job/pingcap/job/tidb/job/ghpr_unit_test/1981/): used 146590ms
Contributor guide
Research direction
Start with the TestIndexMergePanic test in pkg/executor/test/indexmergereadtest and run it to confirm the reported runtime. Trace why this test takes about 144 seconds, then verify that its execution time is substantially reduced without changing the intended test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100