Travis build not working about excoveralls

[parroty]

Thanks for the report. Is there any way to get more detailed information? (git repo would be nice, but at least related code like mix.exs and elixir version would help). A push couple days ago in my repo was working at Travis, and I would like to isolate the condition.

[pspeter3]

Unfortunately I deleted that repository but I'm trying to reproduce it. On a side note, do you know if excoveralls works with umbrella projects?

[parroty]

Thanks. It may not work well with umbrella projects at the moment.. At parent app, it seems [mix test] tasks are invoked multiple times for each of the child apps, and I don't have coordination mechanism yet (I can observe some weird behavior with my brief experiment).
It may be possible to make it work at least locally, but need more thinking for travis execution.

[pspeter3]

Yeah I got it to work locally but could not get it to work on Travis which is unfortunate but understandable.

[parroty]

Was the original issue occur on the umbrella project?

[pspeter3]

No, I'm sorry for conflating the two issues. The original issue was with travis when I used the below to get the faster container builds.

sudo: false

[my-flow]

I'm seeing the exact same SSL issue with my repository at https://github.com/my-flow/mt940. The travis build is here: https://travis-ci.org/my-flow/mt940
@parroty is there a problem with the host name verification?

[parroty]

Thanks for the information. I could simulate the error by forking your repository. I haven't been able to identify the issue yet, I could partially make it work for erlang 17.1 (though failing on 17.3...).

https://github.com/parroty/mt940
https://travis-ci.org/parroty/mt940/builds/62483907
https://coveralls.io/r/parroty/mt940

I'll check more later about isolating the issue (erlang 17.3 seems working on other my repository). Maybe it's good to upgrade hackney to the latest, etc.

I'm not sure about the host name verification (it's about ssl_verify_hostname package?).

[my-flow]

Good catch! According to this Stackoverflow link it is a "known bug in Erlang OTP 17.3". I upgraded to 17.4 and that solved my problem. Thanks!

[parroty]

Thanks for the reference!