forked from cockroachdb/cockroach
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
36224: roachtest: after test, fail (or complain) if any CRDB nodes are dead r=andreimatei a=tbg Do what's in the title. This will help us ensure that no test leaves dead nodes behind (maybe some tests do that today, perhaps some chaos ones, 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 ``` Release note: None 36279: exec: minor refactor of test utilities to reduce confusion r=yuzefovich a=yuzefovich Release note: None Co-authored-by: Tobias Schottdorf <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]>
- Loading branch information
Showing
10 changed files
with
200 additions
and
57 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
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
Oops, something went wrong.