From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: pidge@toganlabs.com, "Randle,
William C" <william.c.randle@intel.com>,
"Lock, Joshua G" <joshua.g.lock@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [yocto-autobuilder] [RFC] Add support for generate bitbake error reports
Date: Thu, 9 Jun 2016 16:23:11 -0500 [thread overview]
Message-ID: <5759DE3F.9040002@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2297 bytes --]
Hi folks,
Currently we support to send error reports to errors.yoctoproject.org
about failing tasks on bitbake using SendErrorReport buildstep but we
have a lack of bitbake related errors like exceptions.
A bug exist to implement this support into Error report web [1], i'm
working on it but for generate bitbake error reports there's a need of
some process monitoring the bitbake output in this case the Yocto
Autobuilder.
This email is for review my current implementation for generate bitbake
error reports in the Autobuilder [2] next i'll try to explain how it works.
I aadded a BitbakeShellCommand [3] class for use in the buildsteps that
executes bitbake the main objective of this class is to have common
operations to be made in bitbake commands like create error reports if
fails.
For create error reports this class add an stdio observer to look at
bitbake output and if bitbake fails review the bitbake output for
identify if the failure is an non-related task error [4]. If the
observer found bitbake error creates an Error report with the
information in the master controller.
In order to send the bitbake error to Error report web the controller
transfer the report to the worker using a new DownloadDirectory
implementation that i made [5], the SendErrorReport buildstep works on
the worker side so it's easy to transfer the reports from master to
worker instead of send it by master.
Finally to complete with the job of have the bitbake errors reports the
Error report web changes need (i'm working on it) to be integrated
first in order to don't break anything.
Please review it and provide me feedback.
Cheers,
alimon
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7583
[2]
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log/?h=contrib/alimon/devel
[3]
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py?h=contrib/alimon/devel#n92
[4]
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py?h=contrib/alimon/devel#n53
[5]
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?h=contrib/alimon/devel&id=4022920bb0e56d1eef3dfe7c5e9b4699f801cdf1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2016-06-09 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 21:23 Aníbal Limón [this message]
2016-06-13 8:48 ` [yocto-autobuilder] [RFC] Add support for generate bitbake error reports Beth 'pidge' Flanagan
2016-06-13 15:09 ` Aníbal Limón
2016-06-13 15:52 ` Beth 'pidge' Flanagan
2016-06-14 15:16 ` Joshua G Lock
[not found] ` <1465916993.2814.14.camel@intel.com>
2016-06-14 15:57 ` Aníbal Limón
2016-06-14 17:03 ` Aníbal Limón
2016-06-15 13:19 ` Joshua G Lock
2016-06-15 14:07 ` Aníbal Limón
2016-06-15 14:13 ` Joshua G Lock
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=5759DE3F.9040002@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=joshua.g.lock@intel.com \
--cc=pidge@toganlabs.com \
--cc=william.c.randle@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.