-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure log output is reasonable #117
Comments
pjenvey
added a commit
that referenced
this issue
Feb 14, 2020
in --release mode fail tests w/ excessive logging levels (unless explicitly stated w/ @max_logs) Closes #117
pjenvey
added a commit
that referenced
this issue
Feb 14, 2020
in --release mode fail tests w/ excessive logging levels (unless explicitly stated w/ @max_logs) Closes #117
pjenvey
added a commit
that referenced
this issue
Feb 18, 2020
in --release mode fail tests w/ excessive logging levels (unless explicitly stated w/ @max_logs) and fix the Queue import now that python-future is no longer a dependency Closes #117
pjenvey
added a commit
that referenced
this issue
Feb 19, 2020
in --release mode fail tests w/ excessive logging levels (unless explicitly stated w/ @max_logs) - fix the Queue import now that python-future is no longer a dependency - update http per RUSTSEC-2019-0033 + 0034 Closes #117
pjenvey
added a commit
that referenced
this issue
Feb 19, 2020
in --release mode fail tests w/ excessive logging levels (unless explicitly stated w/ @max_logs) - fix the Queue import now that python-future is no longer a dependency - update http per RUSTSEC-2019-0033 + 0034 Closes #117
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our integration tests run autopush-rs, then fire off test_integration.py against it.
Let's add a check to test_integration ensuring autopush-rs's log output is reasonable: that it's not logging an excessive amount of statements during the test run. It should log probably less than a few lines during the test run (this might depend on whether it was built in debug vs release mode).
This would act as a fail-safe for the recent issue where the log trace level was mistakenly enabled.
The text was updated successfully, but these errors were encountered: