(ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io', reason: tls_alert #254

sobolevn · 2021-03-17T05:57:30Z

Hi! I have got a CI fail recently:

Run mix coveralls.github
........................................................................................................................

Finished in 0.6 seconds
35 doctests, 85 tests, 0 failures

Randomized with seed 44094

05:52:09.001 [info]  TLS :client: In state :wait_cert_cr at ssl_handshake.erl:1887 generated CLIENT ALERT: Fatal - Unknown CA

** (ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io' (reason: {:tls_alert, {:unknown_ca, 'TLS client: In state wait_cert_cr at ssl_handshake.erl:1887 generated CLIENT ALERT: Fatal - Unknown CA\n'}}).
    (excoveralls 0.14.0) lib/excoveralls/poster.ex:21: ExCoveralls.Poster.execute/2
    (mix 1.11.4) lib/mix/tasks/test.ex:373: Mix.Tasks.Test.do_run/3
    (mix 1.11.4) lib/mix/task.ex:394: Mix.Task.run_task/3
    (excoveralls 0.14.0) lib/mix/tasks.ex:54: Mix.Tasks.Coveralls.do_run/2
    (mix 1.11.4) lib/mix/task.ex:394: Mix.Task.run_task/3
    (mix 1.11.4) lib/mix/cli.ex:84: Mix.CLI.run_task/2
    (elixir 1.11.4) lib/code.ex:931: Code.require_file/2

Versions:

excoveralls@0.14.0
elixir: 1.11
beam: 23
ubuntu-20.04

CI job: https://github.com/sobolevn/recase/pull/119/checks?check_run_id=2128079815

The text was updated successfully, but these errors were encountered:

sobolevn · 2021-03-18T07:54:38Z

The same happens for another repo: https://github.com/petrovich/petrovich_elixir/runs/2137664773?check_suite_focus=true

bmquinn · 2021-03-18T16:36:04Z

I'm seeing the same error as well, running elixir 1.11 and erlang 23.1:

Finished in 46.0 seconds
41 doctests, 557 tests, 0 failures

Randomized with seed 318874
16:21:58.889 [info]  TLS :client: In state :wait_cert_cr at ssl_handshake.erl:1887 generated CLIENT ALERT: Fatal - Unknown CA

** (ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io' (reason: {:tls_alert, {:unknown_ca, 'TLS client: In state wait_cert_cr at ssl_handshake.erl:1887 generated CLIENT ALERT: Fatal - Unknown CA\n'}}).
    (excoveralls 0.14.0) lib/excoveralls/poster.ex:21: ExCoveralls.Poster.execute/2
    (mix 1.11.4) lib/mix/tasks/test.ex:373: Mix.Tasks.Test.do_run/3
    (mix 1.11.4) lib/mix/task.ex:394: Mix.Task.run_task/3
    (mix 1.11.4) lib/mix/task.ex:439: Mix.Task.run_alias/5
    (excoveralls 0.14.0) lib/mix/tasks.ex:54: Mix.Tasks.Coveralls.do_run/2
    (mix 1.11.4) lib/mix/task.ex:394: Mix.Task.run_task/3
    (mix 1.11.4) lib/mix/cli.ex:84: Mix.CLI.run_task/2
    (elixir 1.11.4) lib/code.ex:931: Code.require_file/2

I think the fix could be bumping to Hackney 1.17.0 (https://github.com/benoitc/hackney/releases/tag/v1.17.0), which adds SSL compatibility with erlang OTP 23

ajvondrak · 2021-03-18T18:11:46Z

Same issue on Elixir 1.11 (earlier versions are fine), and on both OTP 21 and 23: https://github.com/ajvondrak/remote_ip/actions/runs/665483059

Note that Elixir 1.10 works fine on OTP 21, so I'm not sure it's purely an OTP/Hackney issue.

ajvondrak · 2021-03-18T18:17:11Z

These errors seem to coincide with the latest patch version of Elixir 1.11: https://github.com/elixir-lang/elixir/releases/tag/v1.11.4

Elixir 1.11.4 came out a couple days ago, and now Excoveralls is failing with an error: parroty/excoveralls#254 I expect to revert this change when the bug gets sorted out, but in the meantime I'm checking to make sure that CI still works on v1.11.3.

ajvondrak · 2021-03-18T18:28:24Z

Yeah, Elixir v1.11.3 works fine: https://github.com/ajvondrak/remote_ip/runs/2142427054?check_suite_focus=true

The suspicious thing in the v1.11.4 release notes is that rebar was bumped to v3.14.4: https://github.com/erlang/rebar3/releases/tag/3.14.4 But it looks like rebar3 had a lot of changes for that version, so I'm not sure where to begin sifting through those.

bmquinn · 2021-03-18T20:11:38Z

Thanks @ajvondrak, digging into those rebar3 release notes it looks like certifi/erlang-certifi#46 is the likely culprit here

xinz · 2021-04-08T07:12:13Z

Thanks all, same issue with Elixir 1.11.4, after run mix deps.update certifi resolve this issue for me, hope it is helpful for your reference.

rlopzc · 2021-04-12T14:50:09Z

@xinz comment fixed it for me!! I spent a lot trying to find the answer

christhekeele · 2021-04-22T22:31:01Z

I had the same issue, and @xinz 's note to run mix deps.update certifi worked perfectly too, thanks!

Suggested in parroty/excoveralls#254

and fix this issue: parroty/excoveralls#254

parroty/excoveralls#254

* Use amqp's ability to use both URI & conn-options Bumped the amqp version as this ability was introduced in amqp 1.3.0: pma/amqp#144 * Update certifi parroty/excoveralls#254 * Bump CI version

Tests are passing, but CI is failing due to the old excoveralls issue seen before in parroty/excoveralls#254 However, the latest workarounds noted on that issue are for earlier versions of excoveralls that still used hackney instead of httpc (cf. parroty/excoveralls#311). So it's not clear that there are any good/known workarounds, as in the old issue. In particular, we should be running the latest castore version, and I don't think installing/updating certifi is going to do anything. The tests seem to pass on the other Elixir versions in the matrix, but they're all running at least OTP 23. So I'm wondering if OTP 23 would unstick Elixir 1.12 & 1.13. Not ideal, but worth a shot.

ajvondrak · 2024-06-10T00:27:08Z

Heads up that I was getting this error again circa excoveralls 0.18.1. Since #311 moved from hackney to httpc, the certifi update mentioned above wouldn't make a difference AFAICT. However, I noticed that I was only seeing the issue using OTP 22 in my build matrix, so I tried out OTP 23 and that seems to work (even on the same Elixir versions, 1.12 & 1.13).

Before: https://github.com/ajvondrak/remote_ip/actions/runs/9440358658/job/25999841516#step:8:19

After: https://github.com/ajvondrak/remote_ip/actions/runs/9440538202/job/25999999662#step:8:16

asaaki added a commit to asaaki/cmark.ex that referenced this issue May 16, 2021

Update certifi to get coverage reporting working

9d53cf8

Suggested in parroty/excoveralls#254

marcelotto added a commit to rdf-elixir/rdf-ex that referenced this issue May 22, 2021

Update certifi to get coverage reporting working again

db6be78

and fix this issue: parroty/excoveralls#254

b1az added a commit to b1az/conduit_amqp that referenced this issue Nov 18, 2021

Update certifi

3722eae

parroty/excoveralls#254

ajvondrak mentioned this issue Nov 15, 2022

Support to Elixir 1.14 ajvondrak/remote_ip#31

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io', reason: tls_alert #254

(ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io', reason: tls_alert #254

sobolevn commented Mar 17, 2021

sobolevn commented Mar 18, 2021

bmquinn commented Mar 18, 2021

ajvondrak commented Mar 18, 2021 •

edited

Loading

ajvondrak commented Mar 18, 2021

ajvondrak commented Mar 18, 2021

bmquinn commented Mar 18, 2021

xinz commented Apr 8, 2021

rlopzc commented Apr 12, 2021

christhekeele commented Apr 22, 2021

ajvondrak commented Jun 10, 2024

(ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io', reason: tls_alert #254

(ExCoveralls.ReportUploadError) Failed to upload the report to 'https://coveralls.io', reason: tls_alert #254

Comments

sobolevn commented Mar 17, 2021

sobolevn commented Mar 18, 2021

bmquinn commented Mar 18, 2021

ajvondrak commented Mar 18, 2021 • edited Loading

ajvondrak commented Mar 18, 2021

ajvondrak commented Mar 18, 2021

bmquinn commented Mar 18, 2021

xinz commented Apr 8, 2021

rlopzc commented Apr 12, 2021

christhekeele commented Apr 22, 2021

ajvondrak commented Jun 10, 2024

ajvondrak commented Mar 18, 2021 •

edited

Loading