From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 1DCA7E009DF; Fri, 19 Jun 2015 03:30:33 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NORMAL_HTTP_TO_IP, RCVD_IN_DNSWL_LOW,WEIRD_PORT autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.212.180 listed in list.dnswl.org] * 0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP * 0.0 NORMAL_HTTP_TO_IP URI: URI host has a public dotted-decimal IPv4 * address * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5EB6EE009D6 for ; Fri, 19 Jun 2015 03:30:29 -0700 (PDT) Received: by wibdq8 with SMTP id dq8so14385132wib.1 for ; Fri, 19 Jun 2015 03:30:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BtjxkaXKZGdvVugoRDZu4fCrqI2yMzqCsScmlTQ+KZQ=; b=MS3sVrvWnZhjhah22VgBHIRMIpLAb3/E66jcsUBJH1H2MHTLbnYND2W0vgn21qfBsu modEPXHnlLJVYxhnsuggrXX/ZlMGHwLHj0rV0xAM5wo868jyz8jPi5RT22P8/Df+M82+ TUSMlvJm5vugL2Ye0S1RUtpVMg+OlSYa5j+F3Op8zjv7SyiNfYDW6uyIP9UrocuzupX9 CGFxgHlHGuF7Ad3SFf4rD3oJkPBNAT5sKYUooOt7b88ritwayiXZ0Cz0h3U7zT78+r9h HRHMEeX2E2tqutFV26jQjwJkkRrdJH6rcCY5CAbYZdHJmRjGECpA3q2J7N9Hzbq/ZNId CoLw== X-Gm-Message-State: ALoCoQmySR6Dpb0jGmizGDiTtHrd9HlnemO5nXPIhd5cF5wy79wynP5JQfx3fwcFjYAjTKUdL0pb X-Received: by 10.194.58.109 with SMTP id p13mr15021032wjq.36.1434709828716; Fri, 19 Jun 2015 03:30:28 -0700 (PDT) Received: from [192.168.2.73] ([83.217.123.106]) by mx.google.com with ESMTPSA id di7sm3043328wib.23.2015.06.19.03.30.27 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Jun 2015 03:30:28 -0700 (PDT) Message-ID: <5583EF43.1090905@intel.com> Date: Fri, 19 Jun 2015 11:30:27 +0100 From: Michael Wood User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: toaster@yoctoproject.org References: <96FAA1BA813F74449E9A4D20829E33D056CF052F@EU-MBX-03.mgc.mentorg.com> <96FAA1BA813F74449E9A4D20829E33D056CF0548@EU-MBX-03.mgc.mentorg.com> <557FF9B6.5010805@intel.com> <96FAA1BA813F74449E9A4D20829E33D056CF07F8@EU-MBX-03.mgc.mentorg.com> In-Reply-To: <96FAA1BA813F74449E9A4D20829E33D056CF07F8@EU-MBX-03.mgc.mentorg.com> Subject: Re: Query regarding toaster setup X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 10:30:33 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 19/06/15 07:19, Haridasan, Sujith wrote: > Hi Michael Wood, > > Ok as of now I wanted to see how toaster builds a recipe. So I added meta-qt5 layer to the build ( by selecting Yocto master in the intial page where we mention project name). > Then I triggered the build for qtbase. And below is the log I am getting: > > snip > Verifying the Build Environment. If the local Build Environment is not properly configured, you will be asked to configure it. > > Toaster can use a SINGLE predefined configuration file to set up default project settings and layer information sources. > > Toaster will list now the configuration files that it found. Select the number to use the desired configuration file. > [1] - /home/sujith/MEL/mytest/poky/meta-yocto/conf/toasterconf.json > [2] - /home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta-yocto/conf/toasterconf.json > > [0] - Exit without importing any file > > Enter your option: 2 > Importing file: /home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta-yocto/conf/toasterconf.json > Layer configuration imported. Updating information from the layer sources, please wait. > You can re-update any time later by running bitbake/lib/toaster/manage.py lsupdates The script has accidentally picked up a toasterconf.json that was cloned by toaster it's self[1], so this may cause an issue, but I'm not seeing any build execution error, Alex (CC'd) who works on this area of toaster will be better placed to help. [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7741 (Just submitted a patch for this one) > Fetching branches > Fetching layer information > Fetching machine information > Fetching target information > Starting webserver... > Webserver address: http://0.0.0.0:8000/ > Starting browser... > Toaster is now running. You can stop it with Ctrl-C > 2015-06-18 21:27:45,761 DEBUG runbuilds: starting build My Toaster Project (Release master (master), BBV master (Branch: master)) in progress, environment BuildEnvironment object > 2015-06-18 21:27:45,765 DEBUG localhostbecontroller, our git repos are {(u'git://git.openembedded.org/meta-openembedded', u'master'): [(u'meta-ruby', > u'meta-ruby')], > (u'git://git.yoctoproject.org/poky.git', u'master'): [('bitbake', > u'bitbake'), > (u'openembedded-core', > u'meta'), > (u'meta-yocto', > u'meta-yocto'), > (u'meta-yocto-bsp', > u'meta-yocto-bsp')], > (u'git://github.com/meta-qt5/meta-qt5.git', u'master'): [(u'meta-qt5', u'')]} > 2015-06-18 21:27:45,789 DEBUG localhostbecontroller: giturl git://git.yoctoproject.org/poky.git:master checking out in current directory /home/sujith/MEL/mytest/_poky_master.toaster_cloned > 2015-06-18 21:27:45,793 DEBUG localhostbecontroller: checking out commit master to /home/sujith/MEL/mytest/_poky_master.toaster_cloned > 2015-06-18 21:27:47,020 DEBUG localhostbecontroller: selected poky dir name /home/sujith/MEL/mytest/_poky_master.toaster_cloned > 2015-06-18 21:27:47,021 DEBUG localhostbecontroller: localdirpath expected '/home/sujith/MEL/mytest/_poky_master.toaster_cloned/bitbake' > 2015-06-18 21:27:47,021 DEBUG localhostbecontroller: localdirpath expected '/home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta' > 2015-06-18 21:27:47,021 DEBUG localhostbecontroller: localdirpath expected '/home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta-yocto' > 2015-06-18 21:27:47,021 DEBUG localhostbecontroller: localdirpath expected '/home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta-yocto-bsp' > 2015-06-18 21:27:47,021 DEBUG localhostbecontroller: giturl git://git.openembedded.org/meta-openembedded:master checking out in current directory /home/sujith/MEL/mytest/_meta-openembedded_master.toaster_cloned > 2015-06-18 21:27:47,024 DEBUG localhostbecontroller: checking out commit master to /home/sujith/MEL/mytest/_meta-openembedded_master.toaster_cloned > 2015-06-18 21:27:48,441 DEBUG localhostbecontroller: localdirpath expected '/home/sujith/MEL/mytest/_meta-openembedded_master.toaster_cloned/meta-ruby' > 2015-06-18 21:27:48,441 DEBUG localhostbecontroller: giturl git://github.com/meta-qt5/meta-qt5.git:master checking out in current directory /home/sujith/MEL/mytest/_meta-qt5_master.toaster_cloned > 2015-06-18 21:27:48,444 DEBUG localhostbecontroller: checking out commit master to /home/sujith/MEL/mytest/_meta-qt5_master.toaster_cloned > 2015-06-18 21:27:50,252 DEBUG localhostbecontroller: localdirpath expected '/home/sujith/MEL/mytest/_meta-qt5_master.toaster_cloned/' > 2015-06-18 21:27:50,253 DEBUG localhostbecontroller: current layer list [u'/home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta', > u'/home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta-yocto', > u'/home/sujith/MEL/mytest/_poky_master.toaster_cloned/meta-yocto-bsp', > u'/home/sujith/MEL/mytest/_meta-openembedded_master.toaster_cloned/meta-ruby', > u'/home/sujith/MEL/mytest/_meta-qt5_master.toaster_cloned'] > 2015-06-18 21:27:50,335 DEBUG localhostbecontroller: running the listener at /home/sujith/MEL/mytest/poky/bitbake/bin/bitbake > 2015-06-18 21:27:50,335 DEBUG localhostbecontroller: starting builder > bash -c "source /home/sujith/MEL/mytest/_poky_master.toaster_cloned/oe-init-build-env /home/sujith/MEL/mytest/build 2>&1 >toaster_server.log && bitbake --read /home/sujith/MEL/mytest/build/conf/toaster-pre.conf --postread /home/sujith/MEL/mytest/build/conf/toaster.conf --server-only -t xmlrpc -B 0.0.0.0:0 2>&1 >>toaster_server.log " > > 2015-06-18 21:27:50,829 DEBUG localhostbecontroller: Found bitbake server port 46170 > > 2015-06-18 21:27:50,831 DEBUG localhostbecontroller: Waiting bitbake server to start > 2015-06-18 21:27:51,332 DEBUG localhostbecontroller: Waiting bitbake server to start > 2015-06-18 21:27:51,834 DEBUG localhostbecontroller: Waiting bitbake server to start > 2015-06-18 21:27:52,335 DEBUG localhostbecontroller: Waiting bitbake server to start > 2015-06-18 21:27:52,836 DEBUG localhostbecontroller: Started bitbake server > 2015-06-18 21:27:52,864 DEBUG runbuilds: Build launched, exiting. Follow build logs at /home/sujith/MEL/mytest/build/toaster_ui.log > > The toaster_ui.log is as follows: > sujith@kdekid:~/MEL/mytest$ tail -f /home/sujith/MEL/mytest/build/toaster_ui.log > core-image-minimal > core-image-sato > meta-toolchain > adt-installer > meta-ide-support > > You can also run generated qemu images with a command like 'runqemu qemux86' > Bitbake server started on demand as needed, use bitbake -m to shut it down > NOTE: ToasterUI waiting for events > ERROR: Command execution failed: > > When I grep for bitbake this is the following output: > sujith@kdekid:~/MEL/mytest$ ps -ef | grep bitbake > sujith 4820 1481 0 Jun18 ? 00:01:28 python /home/sujith/MEL/mytest/_poky_master.toaster_cloned/bitbake/bin/bitbake --read /home/sujith/MEL/mytest/build/conf/toaster-pre.conf --postread /home/sujith/MEL/mytest/build/conf/toaster.conf --server-only -t xmlrpc -B 0.0.0.0:0 > sujith 11030 2866 0 11:49 pts/8 00:00:00 grep --color=auto bitbake > sujith 22830 2097 0 Jun18 pts/7 00:00:28 /bin/sh ./bitbake/bin/toaster > sujith 22892 22830 0 Jun18 pts/7 00:00:00 python ./bitbake/bin/../lib/toaster/manage.py runserver 0.0.0.0:8000 > sujith 22900 22892 2 Jun18 pts/7 00:24:00 /usr/bin/python ./bitbake/bin/../lib/toaster/manage.py runserver 0.0.0.0:8000 > sujith 23788 1481 0 Jun18 ? 00:01:22 python /home/sujith/MEL/mytest/_poky_master.toaster_cloned/bitbake/bin/bitbake --read /home/sujith/MEL/mytest/build/conf/toaster-pre.conf --postread /home/sujith/MEL/mytest/build/conf/toaster.conf --server-only -t xmlrpc -B 0.0.0.0:0 > sujith 23789 1481 0 Jun18 pts/7 00:00:00 /bin/sh -c bash -c "source /home/sujith/MEL/mytest/_poky_master.toaster_cloned/oe-init-build-env-memres -1 /home/sujith/MEL/mytest/build && DATABASE_URL=sqlite3:///home/sujith/MEL/mytest/poky/toaster.sqlite /home/sujith/MEL/mytest/poky/bitbake/bin/bitbake --observe-only -u toasterui --remote-server=0.0.0.0:-1 -t xmlrpc" > sujith 23790 23789 0 Jun18 pts/7 00:00:00 bash -c source /home/sujith/MEL/mytest/_poky_master.toaster_cloned/oe-init-build-env-memres -1 /home/sujith/MEL/mytest/build && DATABASE_URL=sqlite3:///home/sujith/MEL/mytest/poky/toaster.sqlite /home/sujith/MEL/mytest/poky/bitbake/bin/bitbake --observe-only -u toasterui --remote-server=0.0.0.0:-1 -t xmlrpc > sujith 23832 23790 0 Jun18 pts/7 00:04:43 python /home/sujith/MEL/mytest/poky/bitbake/bin/bitbake --observe-only -u toasterui --remote-server=0.0.0.0:-1 -t xmlrpc > sujith@kdekid:~/MEL/mytest$ > > > Any hint what could have been going wrong? > > Thanks, > Sujith H > > > -----Original Message----- > From: toaster-bounces@yoctoproject.org [mailto:toaster-bounces@yoctoproject.org] On Behalf Of Michael Wood > Sent: 16 June 2015 15:56 > To: toaster@yoctoproject.org > Subject: Re: [Toaster] Query regarding toaster setup > > On 16/06/15 10:50, Haridasan, Sujith wrote: >> Forgot to attach toasterconf.json file in previous mail. Hence >> attaching in the mail. >> >> *From:*toaster-bounces@yoctoproject.org >> [mailto:toaster-bounces@yoctoproject.org] *On Behalf Of *Haridasan, >> Sujith >> *Sent:* 16 June 2015 15:16 >> *To:* toaster@yoctoproject.org >> *Subject:* [Toaster] Query regarding toaster setup >> >> Hi, >> > Hi >> I am new to toaster. I am trying to configure toaster with the layers >> already cloned. I created dir >> >> mkdir -p $HOME/MEL/mytest >> >> cd $HOME/MEL/mytest >> >> git clone git://git.yoctoproject.org/poky.git >> >> git clone git://github.com/meta-qt5/meta-qt5.git >> >> git clone git://github.com/openembedded/meta-oe.git >> > I would recommend keeping the toasterconf.json un-modified and using the Import Layer feature in toaster for custom/customised layers. (Under project configuration on the project page select "Import layer") > > Toaster will checkout/clone layers for you before building with the provided layer git details. If you're using modified versions of existing layers, maybe import them as local-meta-ruby so as not to confuse them with the upstream versions. > > The toasterconf is really just used to bootstrap toaster, to provide some project defaults and current release information to toaster. > > >> I have modified $HOME/MEL/mytest/poky/meta-yocto/conf/toasterconf.json >> file with minor assumptions. I have attached toasterconf.json file >> along with the mail. >> >> I tried executing toaster as follows: >> >> sujith@kdekid:~/MEL/mytest/poky$ ./bitbake/bin/toaster >> >> Syncing... >> >> Creating tables ... >> >> Creating table auth_permission >> >> Creating table auth_group_permissions >> >> Creating table auth_group >> >> Creating table auth_user_groups >> >> Creating table auth_user_user_permissions >> >> Creating table auth_user >> >> Creating table django_content_type >> >> Creating table django_session >> >> Creating table django_admin_log >> >> Creating table south_migrationhistory >> >> You just installed Django's auth system, which means you don't have >> any superusers defined. >> >> Would you like to create one now? (yes/no): yes >> >> Username (leave blank to use 'sujith'): >> >> Email address: >> >> Password: >> >> Password (again): >> >> Superuser created successfully. >> >> Installing custom SQL ... >> >> Installing indexes ... >> >> Installed 0 object(s) from 0 fixture(s) >> >> Synced: >> >>> django.contrib.auth >>> django.contrib.contenttypes >>> django.contrib.messages >>> django.contrib.sessions >>> django.contrib.admin >>> django.contrib.staticfiles >>> django.contrib.humanize >>> south >> Not synced (use migrations): >> >> - orm >> >> - bldcontrol >> >> (use ./manage.py migrate to migrate these) >> >> Running migrations for orm: >> >> - Migrating forwards to >> 0021_auto__chg_field_build_project__chg_field_project_bitbake_version__chg_. >> >>> orm:0001_initial >>> orm:0002_auto__add_field_build_timespent >>> orm:0003_timespent >> - Migration 'orm:0003_timespent' is marked for no-dry-run. >> >>> orm:0004_auto__add_field_package_installed_name >>> orm:0005_auto__add_target_image_file__add_target_file__add_field_variablehistor >>> orm:0006_auto__add_field_target_image_size__add_field_target_license_manifest_p >>> orm:0007_auto__add_helptext >>> orm:0008_auto__chg_field_variablehistory_operation__chg_field_recipe_descriptio >>> orm:0009_auto__add_projectvariable__add_projectlayer__add_projecttarget__add_pr >>> orm:0010_auto__add_field_project_branch__add_field_project_short_description__a >>> orm:0011_auto__add_field_projectlayer_dirpath >>> orm:0012_auto__add_field_projectlayer_optional__add_field_projecttarget_task >>> orm:0013_auto__add_release__add_layerversiondependency__add_unique_layerversion >>> orm:0014_auto__chg_field_package_summary__chg_field_layer_summary__chg_field_re >>> orm:0015_auto__add_field_layer_vcs_web_url__add_field_layer_vcs_web_tree_base_u >>> orm:0016_auto__add_field_release_helptext__chg_field_release_branch__add_index_ >>> orm:0017_auto__del_toastersettingdefaultlayer__add_releaselayersourcepriority__ >>> orm:0018_auto__add_field_layer_version_project >>> orm:0019_auto__add_buildartifact >>> orm:0020_auto__add_field_layer_version_local_path__add_field_recipe_pathflags__ >>> orm:0021_auto__chg_field_build_project__chg_field_project_bitbake_version__chg_ >> - Loading initial data for orm. >> >> Installed 0 object(s) from 0 fixture(s) >> >> Running migrations for bldcontrol: >> >> - Migrating forwards to 0008_brarchive. >> >>> bldcontrol:0001_initial >>> bldcontrol:0002_auto__add_field_buildenvironment_sourcedir__add_field_buildenvironment >>> bldcontrol:0003_auto__add_field_brlayer_dirpath >>> bldcontrol:0004_loadinitialdata >> - Migration 'bldcontrol:0004_loadinitialdata' is marked for no-dry-run. >> >>> bldcontrol:0005_auto__add_brerror >>> bldcontrol:0006_auto__add_brbitbake >>> bldcontrol:0007_auto__add_field_buildrequest_environment__chg_field_buildrequest_build >>> bldcontrol:0008_brarchive >> - Migration 'bldcontrol:0008_brarchive' is marked for no-dry-run. >> >> - Loading initial data for bldcontrol. >> >> Installed 0 object(s) from 0 fixture(s) >> >> Toaster needs to know in which directory it can download build log >> files and other artifacts. >> >> Toaster suggests "/home/sujith/MEL/mytest/poky/toaster_build_artifacts/". >> >> Press Enter to select >> "/home/sujith/MEL/mytest/poky/toaster_build_artifacts/" or type the >> full path to a different directory: >> >> Verifying the Build Environment. If the local Build Environment is not >> properly configured, you will be asked to configure it. >> >> -- Validation: The checkout directory must be set. >> >> Toaster needs to know in which directory it should check out the >> layers that will be needed for your builds. >> >> Toaster suggests "/home/sujith/MEL/mytest". If you select this >> directory, a layer like "meta-intel" will end up in >> "/home/sujith/MEL/mytest/meta-intel". >> >> Press Enter to select "/home/sujith/MEL/mytest" or type the full path >> to a different directory (must be a parent of current checkout >> directory): >> >> Verifying the Build Environment. If the local Build Environment is not >> properly configured, you will be asked to configure it. >> >> -- Validation: The build directory must be set. >> >> Toaster needs to know where is your build directory. >> >> The build directory is where all the artifacts created by your builds >> will be stored. Type the full path to the directory (for example: " >> /home/sujith/build")/home/sujith/MEL/mytest/build >> >> Build configuration saved >> >> Verifying the Build Environment. If the local Build Environment is not >> properly configured, you will be asked to configure it. >> >> Toaster can use a SINGLE predefined configuration file to set up >> default project settings and layer information sources. >> >> Toaster will list now the configuration files that it found. Select >> the number to use the desired configuration file. >> >> [1] - /home/sujith/MEL/mytest/poky/meta-yocto/conf/toasterconf.json >> >> [0] - Exit without importing any file >> >> Enter your option: 1 >> >> Importing file: >> /home/sujith/MEL/mytest/poky/meta-yocto/conf/toasterconf.json >> >> Layer configuration imported. Updating information from the layer >> sources, please wait. >> >> You can re-update any time later by running >> bitbake/lib/toaster/manage.py lsupdates >> >> Fetching branches >> >> Fetching layer information >> >> Fetching machine information >> >> Fetching target information >> >> Starting webserver... >> >> Webserver address: http://0.0.0.0:8000/ >> >> Starting browser... >> >> Toaster is now running. You can stop it with Ctrl-C >> >> May I know how can I get meta-qt5 and meta-ruby layer accessible using >> toasterconf.json file? Any pointers would be helpful for me to proceed >> ahead. >> >> Thanks, >> >> Sujith H >> >> >>