TestFailToStartLeader
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 464
- Forks
- 313
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
Which jobs are flaking?
DM-UT
Which test(s) are flaking?
TestFailToStartLeader
[2022-03-12T14:34:07.029Z] FAIL: election_test.go:34: testElectionSuite.TestFailToStartLeader
[2022-03-12T14:34:07.029Z]
[2022-03-12T14:34:07.029Z] election_test.go:106:
[2022-03-12T14:34:07.029Z] c.Assert(leaderID, check.Equals, cfg1.Name)
[2022-03-12T14:34:07.029Z] ... obtained string = "dm-master-2"
[2022-03-12T14:34:07.029Z] ... expected string = "dm-master-1"
Jenkins logs or GitHub Actions link
Anything else we need to know
-
Does this test exist for other branches as well?
-
Has there been a high frequency of failure lately?
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 with election_test.go, especially TestFailToStartLeader at line 34 and the leader assertion around line 106. Run the test repeatedly and review the linked Jenkins log to investigate why dm-master-2 becomes leader instead of dm-master-1. Done means the cause is addressed and the test passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100