Re: Logging into Coverity Connect

[Guy Harris <guy () alum mit edu>]

On Apr 29, 2019, at 12:57 PM, Jaap Keuter <jaap.keuter () xs4all nl> wrote:

> Anyone else having problems with getting to view the defects?

It now seems to be working for me.

For libpcap:

        Last Build Status: In-queue. Your build is in the queue to be analyzed. There are 237 builds ahead of it.

For tcpdump:

        Last Build Status: In-queue. Your build is in the queue to be analyzed. There are 238 builds ahead of it.

(the 238th of which is presumably the libpcap build)

Wireshark has no build pending.

        
https://buildbot.wireshark.org/wireshark-master/builders/Clang%20Code%20Analysis/builds/5045/steps/copy-cov-build-output/logs/stdio

says

        curl: (60) SSL certificate problem: unable to get local issuer certificate
        More details here: https://curl.haxx.se/docs/sslcerts.html

        curl failed to verify the legitimacy of the server and therefore could not
        establish a secure connection to it. To learn more about this situation and
        how to fix it, please visit the web page mentioned above.

libpcap and tcpdump were having certificate issues.  It may be that that's an issue that they fixed, but that it got 
fixed after the current Clang code analysis build tried to submit something to Coverity; if so, we won't get a Coverity 
build until the current Clang code analysis build (which is also the fuzz build) finishes and the next build tries to 
submit a Coverity build.

scan.coverity.com has nothing about any of these issues; the last announcement was the "Please Reset Your Password" 
announcement, presumably from March 2019.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe