Flaky test: TestTTLStatusCache/current_job_owner_id 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_owner_id in pkg/ttl/cache
- Repo: pingcap/tidb
- Package: pkg/ttl/cache
- Case: TestTTLStatusCache/current_job_owner_id
- 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 the pkg/ttl/cache package with the TestTTLStatusCache/current_job_owner_id case, then inspect the latest merged_unit_test build linked in the report. Reproduce the flaky behavior and identify why the test intermittently fails. Done means the test is deterministic and passes reliably on master.
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
- Mostly clear
- Newbie friendliness
- 48/100