fix: Avoid logging to stdout in devtunnel test #3194
Merged
Conversation
This file contains hidden or 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
The device keeps logging to the logger even after `dev.Close()` but doing that with `t.Log` is unsafe (test has ended). This is why `slogtest` was used. `dev.Close()` has a wait on encryption and decryption routines, however, these are left running even after the wait. The implementation uses the WaitGroups in a weird way.
johnstcn
approved these changes
Jul 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The device keeps logging to the logger even after
dev.Close()butdoing that with
t.Logis unsafe (test has ended). This is whyslogtestwas used.dev.Close()has a wait on encryption and decryption routines, however,these are left running even after the wait. The implementation uses the
WaitGroups in a weird way.