Re-enabled test warnings #374
Merged
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
We previously disabled warnings in tests due to an issue with addressable 2.4 that caused huge numbers of warning messages in every test run. That issue has been fixed now, so we can reenable warnings (which should help detect potential issues in new code)
iainbeeston
force-pushed
the
re-enable-test-warnings
branch
from
695bf10 to
49c1c73
Compare
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.
We previously disabled warnings in tests due to an issue with
addressable 2.4 that caused huge numbers of warning messages in every
test run. That issue has been fixed now, so we can reenable
warnings (which should help detect potential issues in new code)