[PATCH 0/7] reporter-bz: make BZ creation customizable
by Denys Vlasenko
reporter-bz gets a new option, -F FMTFILE, which controls
the format of newly created BZs. It can generate a free-form paragraphs
with list of elements in the BZ comment:
Description of problem: comment
Additional info: -analyzer,-count,-duphash,-uuid,-reason,%oneline
and also can specify bug summary (title) and list of elements to attach:
%summary: [abrt][[: %crash_function%]][[: %reason%]][[: TAINTED %tainted_short%]]
%attach: -reported_to,-comment,-reason,%multiline,-coredump,%binary
Denys Vlasenko (7):
reporter-bz: add -F FMTFILE option
make make_description_item_multiline() static
reporter-bz: reinstate "short backtrace" generation
reporter-bz: implement %attach in -F FMTFILE
reporter-bz: make binary attachments have "application/octet-stream"
MIME-type
reporter-bz: implement %summary in -F FMTFILE
Create bugzilla_format_{libreport,kernel}.conf and install them.
libreport.spec.in | 3 +
src/include/internal_libreport.h | 2 -
src/lib/make_descr.c | 1 +
src/plugins/Makefile.am | 6 +-
src/plugins/bugzilla_format.conf | 37 ++
src/plugins/bugzilla_format_kernel.conf | 35 ++
src/plugins/bugzilla_format_libreport.conf | 36 ++
src/plugins/reporter-bugzilla.c | 672 +++++++++++++++++++++++++++-
src/plugins/rhbz.c | 332 ++------------
src/plugins/rhbz.h | 26 +-
10 files changed, 818 insertions(+), 332 deletions(-)
create mode 100644 src/plugins/bugzilla_format.conf
create mode 100644 src/plugins/bugzilla_format_kernel.conf
create mode 100644 src/plugins/bugzilla_format_libreport.conf
--
1.7.7.6
11 years, 6 months
workflows trac#822
by Jiri Moskovcak
Hi,
I just pushed the latest changes to the workflow branch (libreport) and
would liek to ask you to test it and give me some feedback (you can do
even the code review, but I think there's going to be some changes, so
no need to do it too thorough..)
what works:
- reads workflows from /etc/libreport/workflows/ (I wanted to separate
it from the "pure" events)
- shows the workflow selector if there is matching workflow for the
problem type
what doesn't work:
- the config loading/saving (working on it) so the bz will fail, but
ureport and retrace should work fine
- the expert mode is broken
- it used to be activated when g_auto_events == NULL, but now this
variable is set later in the process, this logic needs to change
(working on it)
improvements:
- the workflows are presented by buttons, maybe a radio buttons with a
long description would be better??
--Jirka
11 years, 6 months
[Automatic Bug Reporting Tool - ABRT] #849: rewrite the c/c++ hook to use systemd/journald to get the cores
by fedora-badges
#849: rewrite the c/c++ hook to use systemd/journald to get the cores
-----------------------+-----------------------------------
Reporter: jmoskovc | Owner: crash-catcher@…
Type: defect | Status: new
Priority: major | Milestone: JournalD_Integration
Component: abrt-ccpp | Version:
Keywords: Nov2012 | Blocked By:
Blocking: 847 |
-----------------------+-----------------------------------
- journald intercepts the C/C++ crashes using the same method as ccpp-hook
(core_pattern) which can result in collision - whoever is started later
wins
- the current journald API doesn't seem to provide a way to register a
callback to events, so the only way to detect a new crash is to poll the
journald which feels wrong - the polling is wrong and we want to react to
the crash immediately
- heard rumours that Suse already uses journald to catch cores, so if we
want to make abrt work on Suse we need to support this
--
Ticket URL: <https://fedorahosted.org/abrt/ticket/849>
Automatic Bug Reporting Tool - ABRT <http://fedorahoted.org/abrt/>
Automatic bug reporting tool
11 years, 6 months
[Automatic Bug Reporting Tool - ABRT] #871: move 'reporter-mailx' from post-create event to notify(-dup) event
by fedora-badges
#871: move 'reporter-mailx' from post-create event to notify(-dup) event
--------------------+------------------------------
Reporter: jfilak | Owner: crash-catcher@…
Type: task | Status: new
Priority: major | Milestone:
Component: abrt | Version: 2.0
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------------
For some reasons mailx gets stucked for a while longer than acceptable and
it significantly slows down the rate of processed crashes. Regardless of
the previously described problem mailx is a type of notification thus we
shouldn't abuse post-create event.
In RHEL6, abrtd has been runnig notify event after successful post-create
event since commit a81bae54df4737e6e9a3b05f15cffefd308a4c04 (2011-11-22)
--
Ticket URL: <https://fedorahosted.org/abrt/ticket/871>
Automatic Bug Reporting Tool - ABRT <http://fedorahoted.org/abrt/>
Automatic bug reporting tool
11 years, 6 months