Thanks Joshua! This fix worked. On Fri, Mar 24, 2017 at 6:44 AM, Joshua Lock <joshua.g.l...@linux.intel.com> wrote:
> Hi Alain, > > On Thu, 2017-03-23 at 17:40 -0400, Alain Achkar wrote: > > I followed http://git.yoctoproject.org/cgit.cgi/ > yocto-autobuilder/tree/README-QUICKSTART > and got: > > > <snip> > > checking controller.cfg > LOADING CONFIG FILE > *error while parsing config file:* > Traceback (most recent call last): > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/Twisted-12.2.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", > line 1187, in unwindGenerator > return _inlineCallbacks(None, gen, Deferred()) > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/Twisted-12.2.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", > line 1045, in _inlineCallbacks > result = g.send(result) > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/buildbot-0.8.8-py2.7.egg/buildbot/scripts/upgrade_master.py", > line 169, in upgradeMaster > master_cfg = loadConfig(config, configFile) > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/buildbot-0.8.8-py2.7.egg/buildbot/scripts/upgrade_master.py", > line 53, in loadConfig > config['basedir'], configFileName) > --- <exception caught here> --- > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/buildbot-0.8.8-py2.7.egg/buildbot/config.py", line 149, in > loadConfig > exec f in localDict > File "/media/data/yocto-autobuilder/yocto-controller/controller.cfg", > line 94, in <module> > yocto_buildsets.createBuildsets() > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/autobuilder/Autobuilder.py", line 65, in createBuildsets > self.parseBuildSet(buildset) > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/autobuilder/Autobuilder.py", line 102, in parseBuildSet > self.parseRepos(buildset) > File "/media/data/yocto-autobuilder/lib/python2.7/ > site-packages/autobuilder/Autobuilder.py", line 127, in parseRepos > if layer.iterkeys().next() not in self.repos: > *exceptions.AttributeError: 'list' object has no attribute 'iterkeys'* > > > I appear to have left a stray comma in buildset-config.controller/nightly.conf > which causes the parser to choke. I've fixed this in the master branch of > yocto-autobuilder: http://git.yoctoproject.org/clean/cgit.cgi/yocto- > autobuilder/commit/?id=239eeaa1e2cf3a985e75f8b75dedfe704a7d6991 > > > You'll need to edit buildset-config/nightly.conf on your local instance > similarly to remove the comma at the end of the repos list, around line 38. > > Thanks for reporting this error! > > Joshua > > Errors loading configuration: > error while parsing config file: 'list' object has no attribute > 'iterkeys' (traceback in logfile) > To start the autobuilder: > ./yocto-start-autobuilder <worker|controller|both> > > To stop the autobuilder: > ./yocto-stop-autobuilder <worker|controller|both> > > >0< alain@esxi-ub1 Thu Mar 23 05:34 PM [master !?] > /media/data/yocto-autobuilder > > > Any ideas on how to fix this? > > On Mon, Nov 14, 2016 at 1:40 PM, Bill Randle <bill.ran...@gmail.com> > wrote: > > Yes, the 2 TB is for everything you might do with an AutoBuilder. The > actual space used will be closer to your 35 GB, since you're building > only a single image / work product. People have used BuilBot directly > for automated builds, but using the AutoBuilder code (which runs > BuildBot underneath) gives you added flexibility and capability > without much additional overhead. > > -Bill > > On Mon, Nov 14, 2016 at 8:13 AM, Alain Achkar <alain.ach...@triacta.com> > wrote: > > Thanks for your answers! From reading these links, it is still not clear > to > > me if this might be overkill for my requirements. AB Cluster Setup talks > > about "the worker requires 2+ TB to hold all the build temp files and git > > repos. If build artifacts and a local sstate mirror are included, > additional > > worker space is required." > > > > Currently, my build only takes 35GB, so I think what these links are > talking > > about is how to replicate what the Autobuilder project > > https://autobuilder.yoctoproject.org/ already does. > > > > To clarify, I am not interested in running builds and tests for > everything > > that Yocto already builds and tests (i.e. all the processor > architectures, > > all the machine types, etc.). I am interested in running one build for > one > > machine type (the Variscite DART-6UL i.MX6UL arm-based processor, for > which > > NXP/Freescale and Variscite have provided recipes and layers for). > > > > I know that autobuilder includes BuildBot (this is why I specified it in > > parentheses) but my question remains: do I only install BuildBot and try > to > > build my machine type with it, or do I install Autobuilder? > > > > On Mon, Nov 14, 2016 at 10:10 AM, Bill Randle <bill.ran...@gmail.com> > wrote: > >> > >> Also, be sure to check the Yocto Project wiki pages: > >> https://wiki.yoctoproject.org/wiki/The_Yocto_Autobuilder > >> in particular, the AB cluster setup and AB maintenance links. Even > >> though the one link refers to setting up an entire cluster, I've used > >> that procedure to setup a single autobuilder, as well. > >> > >> -Bill > >> > >> On Fri, Nov 11, 2016 at 10:37 AM, Beth 'pidge' Flanagan > >> <pi...@toganlabs.com> wrote: > >> > On Fri, 2016-11-11 at 12:35 -0500, Alain Achkar wrote: > >> >> Hello Joshua! > >> >> > >> >> We are using Yocto to build for the Variscite DART-6UL SoM which is > >> >> based on Freescale/NXP i.MX6UL (http://variwiki.com/index.php > ?title=D > >> >> ART-6UL_Yocto_Jethro_R1_build). > >> >> > >> >> Currently, developers run builds manually on their desktops. We are > >> >> considering using a continuous integration server. I found out that > >> >> The Yocto Project uses Autobuilder which in turn uses BuildBot. I > >> >> read most of the introductory documentation. > >> >> > >> >> Would you recommend that we install only BuildBot and configure it to > >> >> build what we need? > >> >> > >> >> OR > >> >> > >> >> Would you recommend that we install Autobuilder (and BuildBot) and > >> >> configure it to build what we need? > >> > > >> > Actually, the yocto-autobuilder already contains buildbot so no need > >> > for both. > >> > > >> > If you read: > >> > > >> > http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/tree/ > README-QUIC > >> > KSTART > >> > > >> > and probably some of the other READMEs and the documentation in the > >> > docs directory of the yocto-autobuilder directory, it should get you > >> > started in the right direction. > >> > > >> > Feel free to ask questions if you need help. > >> > > >> > -b > >> > > >> > Elizabeth 'pidge' Flanagan > >> > Founder/CTO Togán Labs > >> > www.toganlabs.com > >> > > >> >> > >> >> What is the faster path to get up and running? > >> >> > >> >> Thanks! > >> >> Alain. > >> >> > >> >> -- > > >> > > >> > > >> > > >> > -- > >> > _______________________________________________ > >> > yocto mailing list > >> > yocto@yoctoproject.org > >> > https://lists.yoctoproject.org/listinfo/yocto > > > > > > > > > > -- > > > > > -- > > >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
