-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
redis-related test failures #120
Comments
njl
added a commit
to njl/werkzeug
that referenced
this issue
Mar 13, 2012
If the redis library is installed, an attempt is made to automatically run redis unit tests. This might not work if redis is not running, not local, etc, etc, etc. This patch will attempt to connect to redis after the redis import, and will set redis = None if an attempted connection fails, skipping the unit tests for redis as a result.
untitaker
added a commit
to untitaker/werkzeug
that referenced
this issue
Aug 1, 2013
This reverts commit b053873. See also pallets#418
untitaker
added a commit
to untitaker/werkzeug
that referenced
this issue
Apr 18, 2014
This reverts commit b053873. See also pallets#418
untitaker
added a commit
to untitaker/werkzeug
that referenced
this issue
Aug 14, 2014
This reverts commit b053873. See also pallets#418
untitaker
added a commit
to untitaker/werkzeug
that referenced
this issue
Aug 15, 2014
This reverts commit b053873. See also pallets#418
untitaker
added a commit
to untitaker/werkzeug
that referenced
this issue
Aug 15, 2014
This reverts commit b053873. See also pallets#418
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
All redis-related tests fail. redis is installed, but it doesn't mean that it is running. I suggest that test suite automatically run redis or that redis-related tests are skipped.
The text was updated successfully, but these errors were encountered: