Fix build #3
Merged
Fix build #3
Conversation
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
added 3 commits
June 24, 2021 16:22
Signed-off-by: Mathieu Borderé <mathieu.bordere@canonical.com>
tar isn't happy with the changes made in go-dqlite as part of canonical/go-dqlite#147.
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.
More robust filewriting go-dqlite#147 , complains that
file changed as we read itand exits with a non-0 code which causes jepsen to throw an exception when the real test is already done. Because go-dqlite only writes to non-database files I think we can ignore the tar non-0 exit code.