All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Brian Avery <avery.brian@gmail.com>
Cc: toaster@yoctoproject.org
Subject: Re: [PATCH 09/10] toaster-manual: update runbuilds instructions
Date: Tue, 12 Jul 2016 18:36:21 +0300	[thread overview]
Message-ID: <20160712153621.GA819@linux.intel.com> (raw)
In-Reply-To: <CAKV_0eh728iJdaCmbQd0haGeoMcNVtVFW57GT1n+=5LJ-WUO9Q@mail.gmail.com>

Hi Brian,

Thank you for testing this!

On Mon, Jul 11, 2016 at 05:10:22PM -0700, Brian Avery wrote:
> Hi,
> 
> I was trying out your instructions/production setup on an ubuntu
> 16.04/mysql setup and got the following error:
> $>TOASTER_DIR=`pwd` TOASTER_CONF=./meta-poky/conf/toasterconf.json
> ./bitbake/lib/toaster/manage.py checksettings --traceback 2>&1 | tee
> mychecksettings.log
> 
> resulted in
> 
> django.db.utils.DataError: (1406, "Data too long for column 'license' at row 1")

> I'm attaching the logfile.
> 
> Have any of you seen this before? It kinda stops me cold here. Sadly,
> the error doesn't let me know what table or data was too long.
I've reproduced it. It's failing to load linux-firmware recipe:
https://layers.openembedded.org/layerindex/recipe/59/

With this patch it should skip this recipe with the warning:
https://lists.yoctoproject.org/pipermail/toaster/2016-July/004979.html

> p.s. other issues I've seen so far
> 1) 3.7.2.1
> sudo mkdir /var/www/toaster
> need a : sudo chown toaster /var/www/toaster
Fixed by adding -m option to useradd command:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ed/toaster/python3-documentation&id=f1182c2eee4df48f9dd50c76be540fb0c0578c54

> 2) 3.7.2.4
> SECRET_KEY needs a pointer to the Django documentation so people know
> what it is:
> https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SECRET_KEY
Done. SECRET_KEY, STATIC_ROOT and DATABASE became a links to Django
documentation:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ed/toaster/python3-documentation&id=80f58acb788d552a11d8e1dbcaf233a2ba43b301


> 3) 3.7.2.6
> the TOASTER_DIR=... checksettings line is too long and got truncated
> for me when my pdf was made.  We should probably break it in 2 or use
> exports.
Splitted to 2 lines:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ed/toaster/python3-documentation&id=1bdf15510d96a695e1680db0ee95926e22a4996c

I've updated my branch ed/toaster/python3-documentation with all above
changes. please, review.

Regards,
Ed

> On Fri, Jul 8, 2016 at 6:30 AM, Michael Wood <michael.g.wood@intel.com> wrote:
> > Pasting this in as it's an updated version of this patch:
> >
> >
> > commit 74e368b1855bbf4321f73b09a0f2c973b1e33c61
> > Author: Ed Bartosh <ed.bartosh@linux.intel.com>
> > Date:   Mon Jun 27 17:37:40 2016 +0300
> >
> >     toaster-manual: update runbuilds instructions
> >
> >     Added sample configuration files and instructions for the runbuilds
> >     systemd service. Service runs runbuilds in a screen session for user
> >     convenience. User can attach to the session to see the runbuilds output,
> >     monitor logs and build environment.
> >
> >     Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> >
> > diff --git a/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> > b/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> > index febbd15..26e71c8 100644
> > --- a/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> > +++ b/documentation/toaster-manual/toaster-manual-setup-and-use.xml
> > @@ -438,22 +438,49 @@
> >                        </literallayout>
> >                        </para></listitem>
> >                    <listitem><para>
> > -                      Install the build runner service.
> > -                      This service needs to be running in order to dispatch
> > -                      builds.
> > -                      Use this command:
> > +                      Prepare systemd service to run toaster builds.
> > +                      Here is a sample configuration file for the service:
> >                        <literallayout class='monospaced'>
> > -   /var/www/toaster/poky/bitbake/lib/toaster/manage.py runbuilds
> > +   [Unit]
> > +   Description=Toaster runbuilds
> > +
> > +   [Service]
> > +   Type=forking
> > +   User=toaster
> > +   ExecStart=/usr/bin/screen -d -m -S runbuilds
> > /var/www/toaster/poky/bitbake/lib/toaster/runbuilds-service.sh start
> > +   ExecStop=/usr/bin/screen -S runbuilds -X quit
> > +   WorkingDirectory=/var/www/toaster/poky
> > +
> >
> >
> > This is kind of interesting from a developer of Toaster point of view but I
> > don't think we should be recommending screen in the production setup.
> > Toaster should be logging all the useful output anyway.
> >
> >
> >
> > +   [Install]
> > +   WantedBy=multi-user.target
> >                        </literallayout>
> > -                      Here is an example:
> > +                      And the runbuilds-service.sh script that you should
> > put into /var/www/toaster/poky/bitbake/lib/toaster/ and
> > +                      set executable permissions to it.
> >                        <literallayout class='monospaced'>
> > -   #!/bin/sh
> > -   # toaster run builds dispatcher
> > -   cd /var/www/toaster/
> > -   source ./venv/bin/activate
> > -   ./bitbake/lib/toaster/manage.py runbuilds
> > +   #!/bin/bash
> > +
> > +   #export http_proxy=http://proxy.host.com:8080
> > +   #export https_proxy=http://proxy.host.com:8080
> > +   #export GIT_PROXY_COMMAND=$HOME/bin/gitproxy
> > +
> > +   cd ~/poky/
> > +   source ./oe-init-build-env build
> > +   source ../bitbake/bin/toaster $1 noweb
> > +   [ "$1" == 'start' ] &amp;&amp; /bin/bash
> >                        </literallayout>
> > -                      </para></listitem>
> > +                  </para></listitem>
> > +                  <listitem><para>
> > +                      Run the service:
> > +                      <literallayout class='monospaced'>
> > +   # service runbuilds start
> > +                      </literallayout>
> > +                      As service is running in a detached screen session
> > you can attach to it using this command:
> > +                      <literallayout class='monospaced'>
> > +   $ sudo su - toaster
> > +   $ screen -rS runbuilds
> > +                      </literallayout>
> > +                      And detach from it again using 'Ctrl-a' followed by
> > 'd' key combination.
> > +                  </para></listitem>
> >                </orderedlist>
> >                You can now open up a browser and start using Toaster.
> >            </para>
> >
> >
> > --
> > _______________________________________________
> > toaster mailing list
> > toaster@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/toaster



-- 
--
Regards,
Ed


  reply	other threads:[~2016-07-12 15:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 15:24 [PATCH 00/10] Toaster documentation update Ed Bartosh
2016-06-27 15:24 ` [PATCH 01/10] toaster-manual: Switch to pip3 dependency installer Ed Bartosh
2016-06-27 15:24 ` [PATCH 02/10] toaster-manual: update distro versions Ed Bartosh
2016-06-27 15:24 ` [PATCH 03/10] toaster-manual: update list of packages Ed Bartosh
2016-06-27 15:24 ` [PATCH 04/10] toaster-manual: add list of packages for openSUSE Ed Bartosh
2016-06-27 15:24 ` [PATCH 05/10] toaster-manual: add instructions to create user Ed Bartosh
2016-06-27 15:24 ` [PATCH 06/10] toaster-manual: change mysql driver Ed Bartosh
2016-06-27 15:24 ` [PATCH 07/10] toaster-manual: add instructions for OpenSUSE Ed Bartosh
2016-06-27 15:24 ` [PATCH 08/10] toaster-manual: update apache configuration file Ed Bartosh
2016-06-27 15:24 ` [PATCH 09/10] toaster-manual: update runbuilds instructions Ed Bartosh
2016-06-28 15:41   ` Michael Wood
2016-07-05 13:53     ` Ed Bartosh
2016-07-08 13:30   ` Michael Wood
2016-07-12  0:10     ` Brian Avery
2016-07-12 15:36       ` Ed Bartosh [this message]
2016-06-27 15:24 ` [PATCH 10/10] toaster-manual: add OpenSUSE to the list of distros Ed Bartosh
2016-07-08 13:37   ` [PATCH] toaster-manual: Update toaster start documentation Michael Wood
2016-07-13 16:06     ` Brian Avery
2016-07-14 18:14       ` Scott Rifenbark
2016-07-14 23:45         ` Brian Avery

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=20160712153621.GA819@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=avery.brian@gmail.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.