-
Notifications
You must be signed in to change notification settings - Fork 60
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
SSL errors on Travis #81
Comments
Disabling https is a temporary work around: https://travis-ci.org/musoke/inspirer/builds/271306689 Possibly also related: seanmonstar/reqwest#70 |
Disables https when accessing inspire. Travis + trust seems to break reqwest + SSL. japaric/trust#81
Interesting: the errors are not from running the |
I tried a few things here: just rebuilding the Docker image as it is, bumping the OpenSSL version, basing the Docker image on a more recent OS (12.04 -> 14.04) but I still see the same problem. I must admit that I don't understand the root of the problem. A similar problem was reported in cross-rs/cross#119; in that case, a binary compiled with Cross doesn't work when executed on the host (not in the Cross environement) because it panics with some SSL related error. |
Thanks for looking into this! |
Thanks @musoke, I too had this problem and worked around it adding to the
|
Spoke too soon! When I download the release file produced by travis I still get the same error! |
This issue seems to have been resolved. Don't know how or when. |
I'm switching a small project of mine over to trust. Builds on Travis are failing when they didn't previously. I'm getting SSL errors when testing the crate with
TARGET=*-unknown-linux-*
on Travis. darwin is fine, and the tests don't run on BSD or Windows. Testing locally on debian and arch linux also works.It looks like reqwest can't find certificates:
Example log on Travis
Line where the panic happens
This looks like a related issue: #55 . It's not exactly same though; everything seems to build but there is an error during tests.
Thanks for this project!
The text was updated successfully, but these errors were encountered: