From: Andreea Proca <andreea.b.proca@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2 0/1] Error reporting tool
Date: Fri, 14 Feb 2014 13:58:42 +0200 [thread overview]
Message-ID: <cover.1392378926.git.andreea.b.proca@intel.com> (raw)
Changes in v2:
- address RP's comments (rename methods, handler and add an eventmask)
Hello,
This patch together with the web app from git://git.yoctoproject.org/error-report-web.
form an error reporting system similar to kernel-oops service.
This tool proposes a way of keeping track of the errors appeared during builds
by dumping the debug information of the build into a database which can be analyzed.
The project will benefit from the multitude of build results published by quickly identifying the issues and the areas of interest for the contributors.
The objectives of the application were achieved by creating a client-server system. The client (basically this bitbake class) collects all the information needed
for solving the errors and the server receives that data and saves in a database (see the Django web app at git://git.yoctoproject.org/error-report-web).
The data collected consists of the log file of the tasks that failed and common configuration variables
(such as machine, distro, host distro, etc as well as the version of the build system - branch/commit id, which
is commonly missing from bug reports :) ).
All the debug information collected during a build which failed is stored on the user's machine, in a JSON format and its path is displayed
in the output of the build as well as the command that the contributor can run to send the error report file to the server. The
script will give the user a link corresponding to his entry in the database. The scripts accepts a parameter which is the hostname
to the web app instance (by default it's localhost).
Contributors can search by certain configurations (e.g. machine, component, error, task) and see statistics through the web interface.
Thanks,
Andreea
The following changes since commit ee151ed6bc16312733c67b91bbf65959309b640d:
lib/oe/rootfs.py: fix RPM multilib issue (2014-02-13 12:06:01 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib andreeap/report-poky
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=andreeap/report-poky
Andreea Proca (1):
report-error.bbclass: new class to save build information when errors
occur
meta/classes/report-error.bbclass | 66 +++++++++++++++++++++++++++++++
scripts/send-error-report | 78 +++++++++++++++++++++++++++++++++++++
2 files changed, 144 insertions(+)
create mode 100644 meta/classes/report-error.bbclass
create mode 100755 scripts/send-error-report
--
1.7.9.5
next reply other threads:[~2014-02-14 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 11:58 Andreea Proca [this message]
2014-02-14 11:58 ` [PATCHv2 1/1] report-error.bbclass: new class to save build information when errors occur Andreea Proca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1392378926.git.andreea.b.proca@intel.com \
--to=andreea.b.proca@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox