Coverity failures on github

[Dr Paul Dale]

The CIs are trying to run on your fork of the main repository and you've 
not got a Coverity token set up.
To disable the run:

 1. Go to your fork of the repository
    (https://github.com/pprindeville/openssl)
 2. Click onto the "Actions" tab along the top
 3. Click the "Static Analysis" workflow on the bottom left.
 4. Click on the ellipsis button next to the search box (...)
 5. Select "Disable Workflow"



Pauli

On 4/2/22 12:44, Philip Prindeville wrote:
> I'm getting daily reports about static analysis failures:
>
> https://github.com/pprindeville/openssl/runs/5060866030?check_suite_focus=true
>
> Which says:
>
> Run wgethttps://scan.coverity.com/download/linux64  \
>    wgethttps://scan.coverity.com/download/linux64  \
>         --post-data "token=&project=openssl%2Fopenssl" \
>         --progress=dot:giga -O coverity_tool.tgz
>    shell: /usr/bin/bash -e {0}
> --2022-02-04 01:26:39--https://scan.coverity.com/download/linux64
> Resolving scan.coverity.com (scan.coverity.com)... 45.60.34.99
> Connecting to scan.coverity.com (scan.coverity.com)|45.60.34.99|:443... connected.
> HTTP request sent, awaiting response... 401 Unauthorized
>
> Username/Password Authentication Failed.
> Error: Process completed with exit code 6.
>
> Looks like there's an expired Coverity license, or the creds are incorrect?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20220204/83b2429c/attachment.htm>