Home → Questions →

Coveralls SSL Error

• Edit

jtzero

01 May, 2015 07:01 PM

Afternoon all,
I keep getting "SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A" (https://ci.appveyor.com/project/jtzero/vigilem-win32-api/build/15/job/mn3s22a3dwpjr75j) in the vanilla coveralls gem. Coveralls supports AppVeyor, through other discussions it's stated that coveralls.net works, and using environment variables the report gets sent on my machine. However sending in AppVeyor fails, I'm assuming it's my configuration.Any Help? thanks

1. Support Staff 1 Posted by Feodor Fitsner on 01 May, 2015 07:16 PM

   

   Found few links that might shed more light:
   http://stackoverflow.com/questions/23223691/ssl-connect-syscall-ret...
   http://stackoverflow.com/questions/9175151/connecting-using-https-t...

   • Edit

2. 2 Posted by jtzero on 08 Jun, 2015 05:56 PM

   

   I came up with those search results as well, unfortunately coverall's goal is to be two line setup, and ssl_version isn't a config option.
   

   require 'coveralls'
   Coveralls.wear!
   

   1. And so after some plumbing I added a small patch to change :ssl_version => :TLSv1 and it failed
   2. I changed the badge on the readme (commit e12b09c47773e6acf4f45fab7e8fad2f4eff4c0d) and it randomly worked (only on i386)
   3. I removed the other env's that don't work from the appveyor.yml and it failed
   4. rebuilt commit e12b09c47773e6acf4f45fab7e8fad2f4eff4c0d and it passed
   5. I then changed everything back to match commit e12b09c47773e6acf4f45fab7e8fad2f4eff4c0d so there is no difference between build 32 and 33 (did a diff) yet build 33 fails.

   So i don't understand what different between these two, I haven't changed the build settings.

   • Edit

3. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.