Flaky test: TestTTLStatusCache/last_job_ttl_expire 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/last_job_ttl_expire in pkg/ttl/cache
- Repo: pingcap/tidb
- Package: pkg/ttl/cache
- Case: TestTTLStatusCache/last_job_ttl_expire
- 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 in pkg/ttl/cache and locate TestTTLStatusCache/last_job_ttl_expire. Run that test repeatedly, then inspect the linked merged unit-test build and the test's TTL or expiration timing assumptions. Done means the test is reliable and no longer reported as flaky.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100