Skip to content
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

Tests are failing on Travis - here for documentation purposes #175

Closed
johnathanvidu opened this issue Aug 29, 2017 · 0 comments · Fixed by #176
Closed

Tests are failing on Travis - here for documentation purposes #175

johnathanvidu opened this issue Aug 29, 2017 · 0 comments · Fixed by #176

Comments

@johnathanvidu
Copy link
Collaborator

johnathanvidu commented Aug 29, 2017

Issue details

18 tests are currently failing on travis.
Most errors looks like that:

SSLError: HTTPSConnectionPool(host='api.github.com', port=443): Max retries exceeded with url: /repos/quali/resource-test/zipball (Caused by SSLError(SSLError("bad handshake: SysCallError(32, 'EPIPE')",),))

If you encounter this error on travis, scroll down to the Explanation section and investigate

Steps to reproduce

Run travis build and verify that it installs coveralls 1.2.0 (travis.yml configured to install the latest coveralls which is currently 1.2.0)

Explanation

On the 16th August 2017 coveralls released a new version (1.2.0) and thus travis installs the latest version. coveralls has a dependency on urllib3 (through requests) but the new version actually requests the secure version (urllib3[secure]) which installs pyopenssl with it (added in 1.11).
For unknown reasons httpretty doesn't work correctly when pyopenssl is installed (I believe it should but it's probably a versions issues), and so our tests fail. I think this is related

The solution is to pinpoint coveralls to version 1.1, and hope that no other dependency will require pyopenssl or that httpretty will fix the problem.

johnathanvidu added a commit that referenced this issue Aug 29, 2017
for more information take a look at issue #175.

closes #175
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant