assigning of abrt crashes

Colin Walters walters at verbum.org
Tue Aug 17 15:20:18 UTC 2010


On Tue, Aug 17, 2010 at 11:12 AM, Thomas Spura
<tomspur at fedoraproject.org> wrote:
>
> Without a clear way "how to reproduce" it, they can't help here

One advantage of automated collection (or semi-automated like ABRT) is
that given enough crashes, it can be easier to track down the root
cause.  So it's useful to have the report logged, even if we can't
take immediate action on it.

> So some upstream author would help, but what in the cases, they
> don't/can't?

Then keep it around until it becomes useful.

> Ignoring the bugs till the release is EOL is not really an option...

So for the reasons above there's no problem with leaving the report in
the system.  Remember also that a certain percentage of crashes are
going to happen simply due to bad hardware.  We have to accept noise
in the system.  Crashes aren't bugs; they're crashes that may be bugs.


More information about the devel mailing list