On 18-07-13 10:42, Stefan Schmidt wrote: > Hello. > > On 23.05.2018 12:24, Boris Faure wrote: > > I was looking at coverity on Terminology and it is currently not > > analyzing any build since 2018-04-15. The latest reason being: > > > >> The build uploaded has been only partially compiled. We recommend at > >> least 85% capture success to avoid false-positives during analysis. As > >> per last few lines of cov-int/build-log.txt, the percentage of > >> compilation units ready for analysis is 84% which is less than the > >> expected 85% > > > > I've compiled it myself and got 89%. I've uploaded a tarball to > > coverity with that. > > However, I wonder this is not the case with our automated upload of > > those results. Could someone help with that investigation? > > Its been a while you sent this. I still have seeing this problem on > coverity builds from Jenkins but sadly also on a manual build I did. > > Anything special you did to get this working locally for you? What is > your coverity tools version? > > regards > Stefan Schmidt
I'm written a small cron script that runs coverity on terminology on my server every hour if needed, and then upload to coverity. It runs coverity 2017.07. It might be related to the compiler / headers found on the system. I added this stupid patch just for coverity: https://git.enlightenment.org/apps/terminology.git/commit/?id=75689087ae680808cf006f83a2c4dfdc432602d7 Might be useful elsewhere. Regards, -- Boris Faure Pointer Arithmetician
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
