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.

Sign up for GitHub

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

Jump to bottom

Find way to deal with HTTP_PROXY (and friends) env configs when running tests #181

Open

jfhbrook opened this issue Dec 22, 2015 · 1 comment

Owner

jfhbrook commented Dec 22, 2015

If you accidentally have HTTP_PROXY-related env vars configured, this can severely confuse the tests.

Probably the best approach is to document this edge case. If you run into this issue, the easiest thing to do is probably

HTTP_PROXY='' npm test

or similar.

See: #175

jfhbrook mentioned this issue

Reset environment proxy config for some cache and range tests. #175

Closed

Owner Author

jfhbrook commented Sep 26, 2016

This might be solve-able by making the tests use pickleback, sidestepping any request issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment