cockroachdb / cockroachdb/cockroach
sql, test: deduplication of test issues which occur on multiple branches
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
## Summary
A test infrastructure change may lead to the same test failing in multiple release branches within a short period of time. This results in one `C-test-failure` issue being created for each impacted branch. We should look into adding logic to avoid this duplication, instead updating the first such issue to include details of all impacted branches.
## Details
See above
Epic: CRDB-60540
Jira issue: CRDB-60552
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the logic that creates C-test-failure issues, then determine how issues from multiple release branches can be recognized and consolidated; done means one issue contains details for all impacted branches instead of duplicates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100