More integration test fixes #1889
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
Helps so you don't have to enter a password on `sudo` on every run
|
Merging this as-is for now. It helps give a better sense of some of the most frequent causes for integration test failures, which I can use to try to figure out how to squash some bugs in the code or test runner to make the output more useful. Just not the top priority at the moment. |
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.
Skips some integration tests that are always going to fail.
Improves output of integration test failures, so that failures are easier to trace and debug and JUnit annotation in Buildkite is more useful.
As a bonus, patches a dev dependency to get rid of a pesky security warning.