abrt server report: 20121004
davej at redhat.com
Thu Oct 4 15:10:47 UTC 2012
On Thu, Oct 04, 2012 at 11:02:43AM -0400, Dave Jones wrote:
> On Thu, Oct 04, 2012 at 04:52:19PM +0200, Richard Marko wrote:
> > kernel 220 ▁▂▄▅▇▇█
> Nice graphs!
> > What's this about?
> > ------------------
> > These are the statistics generated by ABRT Server deployed on .
> > We are going to send these reports weekly as they should help developers
> > prioritize their work. We expect them to become more and more accurate
> > as more people will start using new versions of ABRT with simplified
> > reporting .
> > Note that kernel is incorrectly blamed as the most destabilized
> > component as we started handling kerneloops reports only last week.
> > Feedback is really appreciated mainly on these topics:
> > - structure of this email,
> > - clustering quality,
> > - backtrace quality,
> > - kerneloops processing.
> Feature request:
> Can you do the same backtrace hashing abrt does, and provide a link to any
> bugs in bugzilla with the abrt_hash in the whiteboard ?
Never mind. It seems you do that, and I was looking at reports where no bug
had been filed. Perhaps print "no bug filed yet" in that case ?
More information about the devel