13
37%
master: 37%

Ran 22 Sep 2017 08:31PM UTC

Files 255

Run time 18s

Badge

Embed ▾

Committed 22 Sep 2017 07:01PM UTC coverage: 73.56% (-0.08%) from 73.641%

Job # T=coverage

Build Type

push

travis-ci

Committed by

vszakats

Commit Message

metalink: fix NSS issue in MultiSSL builds

In MultiSSL mode (i.e. when more than one SSL backend is compiled
in), we cannot use the compile time flag `USE_NSS` as indicator that
the NSS backend is in use. As far as Metalink is concerned, the SSL
backend is only used for MD5, SHA-1 and SHA-256 calculations,
therefore one of the available SSL backends is selected at compile
time, in a strict order of preference.

Let's introduce a new `HAVE_NSS_CONTEXT` constant that can be used
to determine whether the SSL backend used for Metalink is the NSS
backend, and use that to guard the code that wants to de-initialize
the NSS-specific data structure.

Ref: https://github.com/curl/curl/pull/1848

Coverage Stats

19970 of 27148 relevant lines covered (73.56%)

105813.98 hits per line

curl / curl / 6359 / 13
37%
master: 37%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6359.13 (T=coverage)

curl / curl / 6359 / 13 37% master: 37%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6359.13 (T=coverage)

curl / curl / 6359 / 13
37%
master: 37%

README BADGES
x