Coverity scan and GNU Radio

We’ve added GNU Radio to the list of projects on Coverity Scan.

Coverity is a static analysis tool that finds many coding mistakes.

https://scan.coverity.com/faq

If you want to get started contributing to GNU Radio, this is a good
place to find some easy tasks. That said, please take some time to look
at the bugs and make the proper fix and do not just make changes to
silence the messages.

When you commit a fix, please reference the Coverity ID (CID) in the
commit message. For example:

https://github.com/gnuradio/gnuradio/commit/dab30e873a8849712e03c26066909a62c8831880

Find the GNURadio project at:

https://scan.coverity.com/projects

and add yourself to the project to access the analysis. Every Monday,
the scan is updated.

Philip


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Sounds great, it was a good idea!

I got added to the project and I can view the summary for GNU Radio,
however, if I click on “View defects” all I get is an empty page with
no projects. Do I have to configure something?

Alex

On Wed, Oct 2, 2013 at 9:37 PM, Alexandru C. [email protected]
wrote:

Sounds great, it was a good idea!

I got added to the project and I can view the summary for GNU Radio,
however, if I click on “View defects” all I get is an empty page with
no projects. Do I have to configure something?

Never mind - I can now see the project.

Alex

On 10/02/2013 01:56 PM, Ben H. wrote:

If you look at a specific issue, you can edit the meta information about it.

To avoid multiple people going after the same bug, and then ending up
having to throw one person’s work away, should we take advantage of the
“Owner” field and have people assign bugs to themselves as soon as they
start working on it?

Let’s try this this for a while and see how it works out.

Philip

That happened to me for a while, too. It seems to take a while once you
register to actually let you start viewing defects.

Cheers,
Ben

On Wed, Oct 2, 2013 at 7:56 PM, Ben H. [email protected] wrote:

a rush of work that ends up unused. If people only assign a bug to
themselves once they start actually writing code (i.e., don’t claim a bug
if you plan to work on it in the future), it might help avoid this issue,
somewhat.

Hi Ben,

I think what you propose makes sense. When you start working on an issue
assign to yourself - but not before. I can imagine many issues will not
take more than a few days to fix and we can always talk to the assignee
if
an issue has been assigned for a long time.

Alex

On Wed, Oct 2, 2013 at 4:04 PM, Alexandru C. [email protected]
wrote:

start working on it?
I think what you propose makes sense. When you start working on an issue
assign to yourself - but not before. I can imagine many issues will not take
more than a few days to fix and we can always talk to the assignee if an
issue has been assigned for a long time.

Alex

I agree. We’ve been trying to be good about curating the Issues on
gnuradio.org to make sure that anyone assigned is working on it or is
on top of it somehow. We can add Coverity as part of this process and
drop or reassign them as necessary.

Tom

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs