<div dir="ltr"><div>Agreed. For the time being, I've turned off the cert verification and you will get the coverage reports. <br></div><div><br></div><div>We have to check with the Coverity team about this.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 23, 2019 at 3:15 PM Michael Scherer <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Le mardi 23 avril 2019 à 14:00 +0530, Amar Tumballi Suryanarayan a<br>
écrit :<br>
> Looks like the issue with http post to coverity site. Needs to<br>
> refresh the<br>
> keys.<br>
> <br>
> <a href="https://build.gluster.org/job/coverity-nightly/" rel="noreferrer" target="_blank">https://build.gluster.org/job/coverity-nightly/</a><br>
<br>
Problem is on their side, they forgot to include the intermediate<br>
certificate (so curl complain).<br>
<br>
To be fair, that's a mistake I keep doing too, and that's hard to<br>
notice, cause firefox tend to cache the said intermediate certificate,<br>
so you can't see with a casual check. <br>
<br>
Their monitoring should pick it up somehow I hope, and I think we are<br>
not the only impacted person.<br>
-- <br>
Michael Scherer<br>
Sysadmin, Community Infrastructure<br>
<br>
<br>
<br>
</blockquote></div>