[yocto] [yocto-autobuilder] [RFC] Add support for generate bitbake error reports

[Beth 'pidge' Flanagan]

On Mon, 2016-06-13 at 10:09 -0500, Aníbal Limón wrote:
> 
> On 06/13/2016 03:48 AM, Beth 'pidge' Flanagan wrote:
> > 
> > On Thu, 2016-06-09 at 16:23 -0500, Aníbal Limón wrote:
> > > 
> > > 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.
> > > 
> > 
> > 1. fix the commit message to ea1d5b35bc77bad5d2
> > 2. in same, why are you removing buildset-config.controller/poky-
> > tiny.conf? I believe this is still supported (and even if it isn't
> > in
> > master, we maintain backwards compatibility)
> Thanks for notice the removal of poky-tiny it wasn't my intention, i
> did
> an script to update the buildsets and seems that don't work well.
> I'll
> fix the last commit message ea1d5b35bc77bad5d2 and also include the
> poky-tiny buildset.
> 

Great, if you can get this onto a dev cluster (halstead should have
info here on connection), I'd be interested in seeing what a nightly
and a nightly-arm do.

-b

> > 
> > 
> > 
> > As a whole, I like what is being done here. I would like this put
> > on
> > the devel cluster before bringing it into production, just to smoke
> > test this, both with nightly builds and single builds. I can't see
> > anything that would obviously blow up though.
> > 
> > cheers,
> > 
> > 
> > -b
> >