Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Trying to use a logger that sends to t.Log is a problem when goroutines can outlive the main test goroutine. It can cause the test to panic if a write happens after the test exits. In general there is no reason to send output to t.Log because 'go test' writes output to stdout. Fix the data race by removing the logger in the integration test. Output will now go to stdout. Also fixes access to a field that should be read atomicly. Finally the third test requires a lock to access the nodes.
- Loading branch information
Showing
6 changed files
with
17 additions
and
48 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