Today, I've taken a quick look at the coverity stuff, because so far I've only seen coverity reports on the Iu code. I see now that actually all of the other osmocom components are also tested by coverity.
So far I'm only seeing the "Osmocom" coverity project, which contains only the iu build. In fact that's a bit of a misnomer -- I assumed that "Osmocom" would contain all of the osmos, it should be more like 'Osmocom-3G' or 'Osmocom-Iu'.
The other osmos are in coverity projects named "libosmocore", "osmo-bts", etc: https://scan.coverity.com/projects?utf8=%E2%9C%93&search=osmo I see there are "add me to project" buttons e.g. here https://scan.coverity.com/projects/libosmocore so I'm trying that now.
Wouldn't it make sense to redirect all the coverity reports to a mailing list? Probably best would be a new mailing list, to avoid noise on openbsc@, like the gerrit-log@ list.
Are these coverity reports a matter of secrecy, to avoid publishing security holes before we fixed them, in which case the coverity mailing list should be invite-only?
~Neels
On Wed, Sep 21, 2016 at 04:25:00PM +0200, Neels Hofmeyr wrote:
I see there are "add me to project" buttons e.g. here https://scan.coverity.com/projects/libosmocore so I'm trying that now.
It seems at most 3 are allowed to be pending :/
~Neels
Curiously, I see that there are no successful builds for osmo-trx with the advice to contact project owner. Who's that in case of osmo-trx and why builds are failing?
On Wed, Sep 21, 2016 at 04:41:12PM +0200, Max wrote:
Curiously, I see that there are no successful builds for osmo-trx with the advice to contact project owner. Who's that in case of osmo-trx and why builds are failing?
The reason is very simple -- it is completely omitted from the coverity build scripts :)
I could try to add it...
~Neels
On Wed, Sep 21, 2016 at 11:01:01PM +0200, Neels Hofmeyr wrote:
On Wed, Sep 21, 2016 at 04:41:12PM +0200, Max wrote:
Curiously, I see that there are no successful builds for osmo-trx with the advice to contact project owner. Who's that in case of osmo-trx and why builds are failing?
I could try to add it...
After apt-get install --no-install-recommends libuhd-dev uhd-host libusb-1.0-0-dev libboost-dev I have successfully built osmo-trx on our build machine.
So, Holger, if you felt so inclined: put the upload_trx function from coverity_test_osmo_trx.sh into coverity_all.sh and uncomment + put the proper coverity token in it, that should enable osmo-trx on coverity.
And then rm coverity_test_osmo_trx.sh...
~Neels
On 21 Sep 2016, at 23:21, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
On Wed, Sep 21, 2016 at 11:01:01PM +0200, Neels Hofmeyr wrote:
On Wed, Sep 21, 2016 at 04:41:12PM +0200, Max wrote:
Curiously, I see that there are no successful builds for osmo-trx with the advice to contact project owner. Who's that in case of osmo-trx and why builds are failing?
I could try to add it...
After apt-get install --no-install-recommends libuhd-dev uhd-host libusb-1.0-0-dev libboost-dev I have successfully built osmo-trx on our build machine.
So, Holger, if you felt so inclined: put the upload_trx function from coverity_test_osmo_trx.sh into coverity_all.sh and uncomment + put the proper coverity token in it, that should enable osmo-trx on coverity.
just go ahead and enable it. Let's copy the build scripts into the osmo-ci repository as well. Maybe we find another way to pass in the secret token (read from a file?)
thank you holger
Neat.
Who's got admin rights? I've sent requests to be added to osmo-bts, osmo-trx and libosmo-dsp projects but they are still pending. Also, if I forgot smth else than please add me there as well - I don't mind some extra emails from coverity.
On 09/21/2016 11:01 PM, Neels Hofmeyr wrote:
On Wed, Sep 21, 2016 at 04:41:12PM +0200, Max wrote:
Curiously, I see that there are no successful builds for osmo-trx with the advice to contact project owner. Who's that in case of osmo-trx and why builds are failing?
The reason is very simple -- it is completely omitted from the coverity build scripts :)
I could try to add it...
~Neels