All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: [PATCH v2 00/15] per project build directory
Date: Fri, 11 Mar 2016 12:42:35 +0200	[thread overview]
Message-ID: <20160311104235.GA6148@linux.intel.com> (raw)
In-Reply-To: <D305B8BE.760AC%belen.barros.pena@intel.com>

Hi Belen,

Thank you for the review. My comments are below.

On Wed, Mar 09, 2016 at 11:40:04AM +0000, Barros Pena, Belen wrote:
> >This is how to test this:
> > - run toaster
> > - run command line build: build zlib
> 
> This shows a warning about build history not being enabled. I know you
> already know about this, but just for completeness ;)
> 
Should be fixed in v3.

> > - check if it's shown in Toaster UI
> 
> Builds started from CLI do show in the web UI, but once they complete they
> are missing layer and package information. I guess that's connected with
> the build history issue above
> 
Most probably it is.

> > - create project for Yocto master
> > - trigger project build from UI
> 
> The build I triggered from the Toaster web UI from a Yocto master project
> (core-image-minimal) failed with this traceback:
> 
> /bin/sh: 1: source: not found
> 
> Traceback (most recent call last):
>   File 
> "/home/yocto/master/bitbake/lib/toaster/bldcontrol/management/commands/runb
> uilds.py", line 58, in schedule
>     br.brtarget_set.all(), "%d:%d" % (br.pk, bec.be.pk))
>   File 
> "/home/yocto/master/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py
> ", line 261, in triggerBuild
>     self._shellcmd('source %s %s' % (oe_init, builddir), self.be.sourcedir)
>   File 
> "/home/yocto/master/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py
> ", line 70, in _shellcmd
>     raise ShellCmdException(err)
> ShellCmdException: command: source
> /home/yocto/master/_toaster_clones/_git___git.yoctoproject.org_poky_master/
> oe-init-build-env /home/yocto/master/build-toaster-master project
> /bin/sh: 1: source: not found
> 
This is related to your shell (dash on Ubuntu I guess). Should be fixed
in v3.

> After all the above there is only one build directory created, the one
> that was generated when running the build from CLI. Also:
> 
> * I can no longer find the toaster_ui.log file
It will be in build directory. You didn't see it as toaster crashed and
didn't create build directory.

> * It looks like the builds are still using build/sstate-cache and
> build/downloads as SSTATE_DIR and DL_DIR, but I think we agreed that
> projects by default would share those 2 directories, which I guess means
> they have to move outside the build directory, although I could be mistaken
> 
This functionality is implemented in another patchset I think.
I'm going to make it working on top of my changes after I'm done with my
patchset. The same with build cancelation patchset - I'll make it
working after this one is accepted.

> * _toaster_clones is still being created in the root checkout directory,
> which I guess makes sense
> 
> * A pending question is where the toaster-custom-images layer we generate
> when building custom images should be. I had a brief chat with Michael
> about this, and I think we concluded the layer should not be shared across
> projects, which means we should create one per project and they should be
> inside the project build dir. Right now the _meta-toaster-custom directory
> is also in the root checkout directory
It makes sense to me. However, I'd rather not do it until this patchset
is tested and accepted. Otherwise amount of patches and new
functionality in this patchset will grow and it will be harder to
maintain it.

Thank you!
Ed



      reply	other threads:[~2016-03-11 13:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 13:53 [PATCH v2 00/15] per project build directory Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 01/15] xmlrpc: fix bug in setting XMLRPCServer.single_use Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 02/15] toaster: don't start bitbake server Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 03/15] toaster: get rid of noui option Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 04/15] toaster: set BITBAKE_UI environment variable Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 05/15] toasterui: add brbe parameter to buildinfohelper Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 06/15] uievent: improve BBUIEventQueue code Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 07/15] buildinfohelper: improve handling of providermap Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 08/15] toasterui: fix brbe reporting Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 09/15] toaster: remove startBBServer API Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 10/15] toaster: remove release API Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 11/15] toaster: add brbe parameter to triggerBuild Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 12/15] toaster: modified setLayers API Ed Bartosh
2016-03-08 13:53 ` [PATCH v2 13/15] toaster: reimplement triggerBuild Ed Bartosh
2016-03-08 13:54 ` [PATCH v2 14/15] toaster: add new parameter to _shellcmd Ed Bartosh
2016-03-08 13:54 ` [PATCH v2 15/15] toaster: stop bitbake server after the build Ed Bartosh
2016-03-09 11:40 ` [PATCH v2 00/15] per project build directory Barros Pena, Belen
2016-03-11 10:42   ` Ed Bartosh [this message]

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=20160311104235.GA6148@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=belen.barros.pena@intel.com \
    --cc=toaster@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.