Hi everyone,
We're excited to announce that the ABRT server [1] will start publishing to
Fedmsg. Currently there are two general topics available:
* faf.report.threshold{1,10,100,1000,1,10,100} is fired whenever a
crash report occurrence reaches the given thre
In last two weeks these components were crashing the most:
1. kernel seen 56703 times (31% of all reports)
http://retrace.fedoraproject.org/faf/problems/1597313/ RHBZ#1030988
http://retrace.fedoraproject.org/faf/problems/749325/
2. virtuoso-opensource seen 19395 times (11% of all reports)
On Tue, Sep 17, 2013 at 03:57:55PM +0200, Michal Toman wrote:
> In last two weeks these components were crashing the most:
>
> 1. kernel seen 85925 times (52% of all reports)
> https://retrace.fedoraproject.org/faf/problems/1174076/
> https://retrace.fedoraproject.org/faf/problems/120
In last two weeks these components were crashing the most:
1. kernel seen 85925 times (52% of all reports)
https://retrace.fedoraproject.org/faf/problems/1174076/
https://retrace.fedoraproject.org/faf/problems/1209703/
2. xulrunner seen 10191 times (6% of all reports)
https://retrace
In last two weeks these components were crashing the most:
1. kernel seen 88743 times (58% of all reports)
http://retrace.fedoraproject.org/faf/problems/1174076/
http://retrace.fedoraproject.org/faf/problems/909608/
2. xulrunner seen 7513 times (5% of all reports)
http://retrace.fed
Am 22.03.2013 03:42, schrieb Orion Poplawski:
> So, what to do about things like:
>
> http://retrace.fedoraproject.org/faf/problems/464418/
>
> where the crash occurs in end user code?
>
> Frame # Function Binary Source Line
> 0 Vlarge_mat_vec_mult::__Vconfigure
> /ourwork/pr
So, what to do about things like:
http://retrace.fedoraproject.org/faf/problems/464418/
where the crash occurs in end user code?
Frame # FunctionBinary Source Line
0 Vlarge_mat_vec_mult::__Vconfigure
/ourwork/projects/shmuel/DudyTests/Verilator_large_mat_vec_mult/RunOctave/V
On 03/21/2013 09:50 PM, Adam Jackson wrote:
On Thu, 2013-03-21 at 19:16 +0100, Miloslav Trmač wrote:
On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak wrote:
How are problem reports like this updated? How do I say "I built a Mesa
that I think fixes this problem, please change its state to MODIF
On Thu, 2013-03-21 at 19:16 +0100, Miloslav Trmač wrote:
> On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak wrote:
> >> How are problem reports like this updated? How do I say "I built a Mesa
> >> that I think fixes this problem, please change its state to MODIFIED"?
> >
> > - the state is synced
On 03/21/2013 07:20 PM, Adam Williamson wrote:
On Thu, 2013-03-21 at 19:16 +0100, Miloslav Trmač wrote:
On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak wrote:
How are problem reports like this updated? How do I say "I built a Mesa
that I think fixes this problem, please change its state to MO
On 03/21/2013 07:16 PM, Miloslav Trmač wrote:
On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak wrote:
How are problem reports like this updated? How do I say "I built a Mesa
that I think fixes this problem, please change its state to MODIFIED"?
- the state is synced with associated bugzilla t
On Thu, 2013-03-21 at 19:16 +0100, Miloslav Trmač wrote:
> On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak wrote:
> >> How are problem reports like this updated? How do I say "I built a Mesa
> >> that I think fixes this problem, please change its state to MODIFIED"?
> >
> > - the state is synced
On Thu, Mar 21, 2013 at 7:09 PM, Jiri Moskovcak wrote:
>> How are problem reports like this updated? How do I say "I built a Mesa
>> that I think fixes this problem, please change its state to MODIFIED"?
>
> - the state is synced with associated bugzilla tickets periodically
> - if the problem do
On Thu, 2013-03-21 at 19:09 +0100, Jiri Moskovcak wrote:
> On 03/21/2013 06:30 PM, Adam Jackson wrote:
> > On Thu, 2013-03-21 at 16:43 +0100, Richard Marko wrote:
> >
> >> Not sure, take a look at these:
> >> http://retrace.fedoraproject.org/faf/problems/525874/
> >> http://retrace.fedoraproject.or
On 03/21/2013 06:30 PM, Adam Jackson wrote:
On Thu, 2013-03-21 at 16:43 +0100, Richard Marko wrote:
Not sure, take a look at these:
http://retrace.fedoraproject.org/faf/problems/525874/
http://retrace.fedoraproject.org/faf/problems/615049/
How are problem reports like this updated? How do I
On Thu, 2013-03-21 at 16:43 +0100, Richard Marko wrote:
> Not sure, take a look at these:
> http://retrace.fedoraproject.org/faf/problems/525874/
> http://retrace.fedoraproject.org/faf/problems/615049/
How are problem reports like this updated? How do I say "I built a Mesa
that I think fixes thi
On 03/21/2013 04:16 PM, Mamoru TASAKA wrote:
> Josh Boyer wrote, at 03/21/2013 11:18 PM +9:00:
>> On Thu, Mar 21, 2013 at 10:13 AM, Richard Marko
>> wrote:
>>> On 03/21/2013 02:50 PM, Richard Marko wrote:
>>>
>>> In last two weeks these components were crashing the most:
>>>
>>> 1. kernel seen 454
Josh Boyer wrote, at 03/21/2013 11:18 PM +9:00:
On Thu, Mar 21, 2013 at 10:13 AM, Richard Marko wrote:
On 03/21/2013 02:50 PM, Richard Marko wrote:
In last two weeks these components were crashing the most:
1. kernel seen 45496 times (36% of all reports)
http://retrace.fedoraproject.org/
On Thu, Mar 21, 2013 at 10:13 AM, Richard Marko wrote:
> On 03/21/2013 02:50 PM, Richard Marko wrote:
>
> In last two weeks these components were crashing the most:
>
> 1. kernel seen 45496 times (36% of all reports)
> http://retrace.fedoraproject.org/faf/problems/586553/
> http://retrace.
On 03/21/2013 02:50 PM, Richard Marko wrote:
> In last two weeks these components were crashing the most:
>
> 1. kernel seen 45496 times (36% of all reports)
> http://retrace.fedoraproject.org/faf/problems/586553/
> http://retrace.fedoraproject.org/faf/problems/258569/
>
> 2. xulrunner se
In last two weeks these components were crashing the most:
1. kernel seen 45496 times (36% of all reports)
http://retrace.fedoraproject.org/faf/problems/586553/
http://retrace.fedoraproject.org/faf/problems/258569/
2. xulrunner seen 12020 times (9% of all reports)
http://retrace.fed
Hot problems:
ID Components Count
---
185766 kernel 1294
204154 kernel 1198
85820 yumex786
100
Hot problems:
ID Components Count
---
34452 dconf450
28310 kernel 379
228274 kernel 327
100
Hot problems:
ID Components Count
---
186587 kernel 411
186872 kernel 350
185998 gnome-packagekit 212
187
Hot problems:
ID Components Count
---
121163 kernel 344
118396 kernel 316
100107 gnome-packagekit 204
1177
Hot problems:
ID Components Count
---
90599 kernel 406
91614 kernel 303
90633 gnome-packagekit 212
924
Hot problems:
ID Components Count
---
61505 kernel 372
61549 kernel 264
29592 wireshark215
2317
On 10/05/2012 04:48 AM, Adam Williamson wrote:
> On Thu, 2012-10-04 at 11:10 -0400, Dave Jones wrote:
>
>> > 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 yo
On 10/04/2012 08:13 PM, Dave Jones wrote:
> On Thu, Oct 04, 2012 at 11:10:47AM -0400, Dave Jones wrote:
>
> > > 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 m
On Thu, 2012-10-04 at 11:10 -0400, Dave Jones wrote:
> > 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
>
On Thu, Oct 04, 2012 at 11:10:47AM -0400, Dave Jones wrote:
> > 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 wh
On 10/04/2012 05:00 PM, Peter Robinson wrote:
> On Thu, Oct 4, 2012 at 3:52 PM, Richard Marko wrote:
>> Hot problems:
>>
>> ID Components Count
>>
>> ---
>>
>> 11834 GConf2
t; --
> >
> > These are the statistics generated by ABRT Server deployed on [1].
> >
> > 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
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 [1].
>
&g
roblems for GConf2 added
up.
Peter
> These are the statistics generated by ABRT Server deployed on [1].
>
> 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
-11 █▂▁▇▁▃▃
What's this about?
--
These are the statistics generated by ABRT Server deployed on [1].
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
On 09/05/2012 07:47 PM, Dave Jones wrote:
> On Wed, Sep 05, 2012 at 11:39:31AM +0200, Michal Toman wrote:
>
> > We believe this will help developers to better prioritize their
> > work and make debugging easier (crashes in common libraries are
> > grouped into a single problem, for each crash ve
On 05/09/12 19:47, Dave Jones wrote:
followed by 3-4 pages of additional spew.
Which means somebody has problems with reading comprehension:
https://docs.djangoproject.com/en/dev/ref/settings/#debug:
DEBUG
Default: False
A boolean that turns on/off debug mode.
On Wed, Sep 05, 2012 at 11:39:31AM +0200, Michal Toman wrote:
> We believe this will help developers to better prioritize their
> work and make debugging easier (crashes in common libraries are
> grouped into a single problem, for each crash versions of affected
> packages/architectures are li
On 05.09.2012 11:44, J. Randall Owens wrote:
On 09/05/2012 02:39 AM, Michal Toman wrote:
Greetings everybody!
As you may have noticed, new ABRT 2.0.12 has recently been pushed to
Fedora. . . .
F16, F17, F18,& rawhide? Or just F18& rawhide? Or. . . ?
Ohh, sorry - F17, F18 & Rawhide
M.
On 09/05/2012 02:44 AM, J. Randall Owens wrote:
> On 09/05/2012 02:39 AM, Michal Toman wrote:
>> Greetings everybody!
>>
>> As you may have noticed, new ABRT 2.0.12 has recently been pushed to
>> Fedora. . . .
>
> F16, F17, F18, & rawhide? Or just F18 & rawhide? Or. . . ?
>
Partial self-reply:
On 09/05/2012 02:39 AM, Michal Toman wrote:
> Greetings everybody!
>
> As you may have noticed, new ABRT 2.0.12 has recently been pushed to
> Fedora. . . .
F16, F17, F18, & rawhide? Or just F18 & rawhide? Or. . . ?
--
J. Randall Owens | http://www.ghiapet.net/
--
devel mailing list
devel@li
Greetings everybody!
As you may have noticed, new ABRT 2.0.12 has recently been pushed to
Fedora. Besides significant changes in reporting workflow, it also uses
the ABRT server to collect what we call uReports (micro-reports).
uReport is a short (usually < 4kB) fingerprint of the cr
43 matches
Mail list logo
