[llvm-dev] Coverity Scan Needs to be Updated after GitHub Migration
Luke Benes via llvm-dev
llvm-dev at lists.llvm.org
Thu Jun 3 14:00:17 PDT 2021
> * it was often regressing
If there is interest, I'd be willing to help with the cov-build,
> * afaik, nobody but me was paying attention to newly detected defects (if I am wrong, please let me know and I can have a look).
In my experience, a weekly report of new defects helps keep engagement up and issues down. Here is an example:
http://document-foundation-mail-archive.969070.n3.nabble.com/New-Defects-reported-by-Coverity-Scan-for-LibreOffice-td4301033.html
Would a weekly scan report be welcome here?
More information about the llvm-dev
mailing list