ср, 17 июл. 2019 г. в 16:36, Dinko Korunic <[email protected]>:
> Dear Илья, > > I’ve increased your access level to Contributor/Member. I terms of > Travis-CI scans, there are some catch22s with current Coverity suite as it > is compiled against ancient glibc and ancient kernel headers and > requires vsyscall=emulate kernel boot option to properly work — not sure if > that will be possible on Travis VMs at all. > it is possible to run scan on travis-ci, have a look https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/.ci/coverity.sh I am goind to add "if: type == cron" so, coverity scan will not slow smoke testing I see the whole picture as following 1) coverity token is set in travis-ci interface 2) builds are scheduled on cron only 3) build checks whether token is defined or not > > I have actual weekly builds that are auto-published to our Coverity Scan > account and they well, require manual interventions, flagging and some day > to day work to get to more usable levels — let me know if you need a hand > with this. You should have all the access required for doing so right now. > > > Kind regards, > D. > > On 17 Jul 2019, at 13:18, Илья Шипицин <[email protected]> wrote: > > Hello, yep, contributor/member would be nice. Also, I can setup automated > travis-ci scans > > On Wed, Jul 17, 2019, 3:27 PM Dinko Korunic <[email protected]> > wrote: > >> Hey Илья, >> >> Let me know if you would like Contributor/Member role for your account on >> Haproxy Coverity account. I was initially more involved and I have started >> configuring modules and parts of code blocks into coherent units, but >> stopped at some point due to lack of time and interest. >> >> There have been a lot of false positives however, I dare to say even in >> excessive volumes. >> >> > On 17 Jul 2019, at 07:48, Илья Шипицин <[email protected]> wrote: >> > >> > Hello, I played with Coverity. Definitely it shows "issues resolved" >> after bugfixes pushed to git. I know Willy does not like static analysis >> because of noise. Anyway, it finds bugs, why not to use it? >> >> >> Kind regards, >> D. >> >> -- >> Dinko Korunic ** Standard disclaimer applies ** >> Sent from OSF1 osf1v4b V4.0 564 alpha >> >> >> > -- > Dinko Korunic ** Standard disclaimer applies ** > Sent from OSF1 osf1v4b V4.0 564 alpha > >
