Flaky test: TestTTLStatusCache/current_job_start_time in pkg/ttl/cache
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
Automated flaky test report.
Title: Flaky test: TestTTLStatusCache/current_job_start_time in pkg/ttl/cache
- Repo: pingcap/tidb
- Package: pkg/ttl/cache
- Case: TestTTLStatusCache/current_job_start_time
- Branch: master
- Flaky Count: 1
- Time Thresholded Count: 0
- Latest Build: https://prow.tidb.net/jenkins/job/pingcap/job/tidb/job/merged_unit_test/441/
Window: 2026-07-02T00:00:00.000Z → 2026-07-03T00:00:00.000Z
Threshold: 100000 ms
Note: This issue is created for a specific branch; updates may be posted as comments.
Contributor guide
Research direction
Start by running TestTTLStatusCache/current_job_start_time in pkg/ttl/cache and reviewing the surrounding cache test and implementation. Reproduce the reported flake using the linked merged_unit_test build context, then identify and remove the nondeterminism so repeated runs complete reliably without changing the intended TTL status behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100