-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
roachtest: after test, fail (or complain) if any CRDB nodes are dead
Do what's in the title. This will help us ensure that no test leaves dead nodes behind (maybe some tests do that today, but it'll be easy enough to fix). This gives us confidence that when a test passes, none of the nodes died. Additionally, for tests that fail, it will always be obvious that a node died because it is now printed as part of the test output including what gets posted into a Github issue. Example: I changed the test below so that it would start nodes 1-3, immediately stop node 1, and return, resulting in the following test failure: ``` --- FAIL: tpcc/nodes=3/w=max (7.24s) cluster.go:956,context.go:90,cluster.go:942,test.go:1160,test.go:1219: dead node detection: 4: skipped 1: dead 2: 83220 3: 83229 Error: 1: dead ``` I similarly verified that a short TPCC test would succeed without such modifications. I also checked the chaos runner code -- it makes sure to have all nodes restarted by the time it exits, so we should be good on that front as well. Release note: None
- Loading branch information
Showing
6 changed files
with
70 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters