Error when CLIENT_IPCPATH is not present with a useful message#163
Merged
paytonrules merged 2 commits intostagingfrom Apr 15, 2020
Merged
Error when CLIENT_IPCPATH is not present with a useful message#163paytonrules merged 2 commits intostagingfrom
paytonrules merged 2 commits intostagingfrom
Conversation
5fc8045 to
6552e35
Compare
Kinda surprised this wasn't there already. Aren't you all on Macs?
When you forget the CLIENT_IPCPATH the integration tests would fail with no message, because logrus wasn't tied to any output. However if you use Expect here you not only get output, but you get it nicely color-coded by ginkgo.
6552e35 to
f458a99
Compare
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
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 integration tests fail when CLIENT_IPCPATH isn't present would fail without a useful error message. So I gave them one.
Example: