wrong failpoints in integration test
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
- kill_owner_with_ddl
github.com/pingcap/tiflow/cdc/capture/ownerFlushIntervalInject - owner_resign
github.com/pingcap/tiflow/cdc/owner/ChangefeedOwnerDontUpdateCheckpoint
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the integration test references for kill_owner_with_ddl and owner_resign, then inspect the failpoints named in cdc/capture/ownerFlushIntervalInject and cdc/owner/ChangefeedOwnerDontUpdateCheckpoint. Confirm which failpoints each scenario should use and update the test references. Done means both scenarios exercise the intended failpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100