Re: [yocto] [[PATCH][yocto-autobuilder] 1/2] buildsteps/CreateAutoConf.py: Add support for specify MACHINE by build prop
On Wed, 2017-01-18 at 18:13 +, Joshua Lock wrote:
> On Mon, 2017-01-16 at 10:25 -0600, Aníbal Limón wrote:
> >
> > Sometimes is a good idea to could specify a machine to build via a
> > build
> > property.
> Why's that? I can guess but the commit log should really tell me what
> the motivation for the change is.
I agree. Please submit a v2 with a bit better of a commit log.
-b
>
> >
> >
> > Signed-off-by: Aníbal Limón
> > ---
> > .../site-
> > packages/autobuilder/buildsteps/CreateAutoConf.py | 6
> > +-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/lib/python2.7/site-
> > packages/autobuilder/buildsteps/CreateAutoConf.py
> > b/lib/python2.7/site-
> > packages/autobuilder/buildsteps/CreateAutoConf.py
> > index 021f542..7915dd5 100644
> > --- a/lib/python2.7/site-
> > packages/autobuilder/buildsteps/CreateAutoConf.py
> > +++ b/lib/python2.7/site-
> > packages/autobuilder/buildsteps/CreateAutoConf.py
> > @@ -174,7 +174,11 @@ class CreateAutoConf(ShellCommand):
> > fout = fout + 'baselib = \\042${@d.getVar(\\04
> > 7B
> > ASE_LIB_tune-\\047 + (d.getVar(\\047DEFAULTTUNE\\047, True) or
> > \\047INVALID\\047), True) or \\047lib\\047}\\042 \n'
> > if self.distro == "poky-rt":
> > fout = fout +
> > 'PREFERRED_PROVIDER_virtual/kernel="linux-yocto-rt" \n'
> > -machine=self.machine
> > +machine=self.getProperty('custom_machine')
> > +if machine:
> > +self.machine = machine
> > +else:
> > +machine = self.machine
> > if layerversion is not None and int(layerversion) > 1:
> > if self.machine == "atom-pc":
> > machine = self.machine.replace("atom-pc",
> > "genericx86")
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Ignoring Fetch errors for optional source.
On Wed, 2016-12-07 at 13:08 +, Burton, Ross wrote:
>
> On 7 December 2016 at 13:00, Beth 'pidge' Flanagan
> om> wrote:
> > I've an odd use case that I wonder if anyone has a work around/way
> > of
> > doing it.
> >
> > I've a client who has contractors who can't have access to a
> > certain
> > segment of the code base. So for example, a recipe will have a
> > SRC_URI
> > for the main bit that everyone has access to, but an extra src_uri
> > that
> > some people won't have access to.
> >
> > I want to be able to just ignore any fetch/unpack errors if that
> > extra
> > src is unfetchable. Thoughts on how to achieve this?
> >
> One solution would be to have a global variable I_AM_SPECIAL which
> the recipes can use:
>
> SRC_URI = "http://public.com/tarball.tar.gz
> ${@oe.types.boolean(d.getVar("I_AM_SPECIAL")) and
> 'http://private.com/tarball.tar.gz'}"
Yeah, unfortunately, people don't neccessarily know they're special if
you get my meaning.
One way we've been trying this is like so:
try:
fetcher = bb.fetch2.Fetch(extra_uri, d)
fetcher.download()
except:
pass
But this doesn't seem to be catching the fetch error.
-b
> > That might work, and also add determinism.
> > Ross
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Ignoring Fetch errors for optional source.
I've an odd use case that I wonder if anyone has a work around/way of doing it. I've a client who has contractors who can't have access to a certain segment of the code base. So for example, a recipe will have a SRC_URI for the main bit that everyone has access to, but an extra src_uri that some people won't have access to. I want to be able to just ignore any fetch/unpack errors if that extra src is unfetchable. Thoughts on how to achieve this? -b -- Beth 'pidge' Flanagan www.toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Buildbot / Autobuilder / custom?
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. > > -- > Alain Achkar, M.Eng. | Software Engineer > Triacta Power Solutions > (O) 613.256.2868 (C) 613.406.6520 > www.triacta.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] First release meta-arduino layer for the Arduino Yún
Hi all, A few weeks ago at ELCE, Paul Barker and I decided to create a layer for the Arduino Yún. We are now releasing the 0.1 version for Morty to the wider community. Patches welcome of course. -b Hello, We are pleased to announce the 0.1 release of our meta-arduino layer for the Yocto Porject 2.2 "Morty" release. It is available for download at: https://www.toganlabs.com/downloads/bsp/meta-arduino/0.1/meta-arduino-0 .1-morty-2.2.tar.bz or via github at: https://github.com/toganlabs/meta-arduino Name: https://www.toganlabs.com/downloads/bsp/meta-arduino/0.1/meta-ard uino-0.1-morty-2.2.tar.bz Hash: 20c65dee2d091f4f5797c869720ad339aca96f49 Tag: 0.1-morty md5sum: 882fa547011fad0530978f4496ca2f3f sha256sum: cc0a72a4e90b6423e7cc1cb93f47f742d001b2276640d5577170dbb3a3eff2a3 This OpenEmbedded BSP layer supports the Arduino Yún board and is based on previous work from OpenWRT. Future support is planned for the Arduino Industrial 101 board and the Arduino Yún Shield. Maintainers: Beth 'pidge' Flanagan pi...@toganlabs.com Paul Barker p...@paulbarker.me.uk Primary repository: https://github.com/toganlabs/meta-arduino Please send any questions and patches to the yocto@yoctoproject.org mailing list with "[meta-arduino]" in the subject. We are not associated with Arduino LLC in any way. This is solely a community supported alternative to the LininoOS OpenWRT based solution. Support requests and bug reports should go directly to the maintainers and not the nice folks at Arduino. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests
On Wed, 2016-10-12 at 07:28 -0700, Bill Randle wrote: > Hi Robert, > > Then "normal" method to send patches is via direct insertion into the > email, rather than an attachment (see git-send-email). Also, it is > missing a commit comment as the first text in the patch file. > Otherwise, it looks good to me now. > > -Bill I'm going to pull this but please, in the future, follow the above. -b > > 2016-10-09 23:44 GMT-07:00 : > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests
On Mon, 2016-10-10 at 01:44 -0500, gm...@reliableembeddedsystems.com wrote: > A few notes (not picking on this patch but it does point out some design failures and I want to at least get this on folks radar). I've been unhappy with how DeployArtifacts work for sometime. Long ago, when I wrote DeployArtifacts, it was "get it working, we'll refactor later" and that refactor never happened. So I'm up for ideas. I would like a deploy infrastructure that: a. Is distro/image name/etc agnostic (aka, poky and image names and paths hardcoded. ick.). b. Is perhaps config file driven. c. Had much less of the cruft that exists withing DeployArtifacts. So. Thoughts on this? I'd be willing to hear suggestions on how to do this before I go and spend some time ripping this apart post release? -b -- Beth 'pidge' Flanagan toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [[PATCHv5][yocto-autobuilder]] buildset.controller: Add build set to test new OS distribution in autobuilder
On Mon, 2016-10-10 at 09:54 -0500, Aníbal Limón wrote:
> From: Monserrat Sedeno
>
> As part of the process to set new OS distribution as supported on
> Yoctoc Project
> a new patch was created with the list of build sets that should be
> executed.
>
> Detailed information:
> https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan#Execute_Build_
> Sets
>
> Fixes [YOCTO #9905]
>
Is this something that should be on the production servers? If so, I'll
pull it later.
If not, please re-read my prior email. If this is going to be on it's
own ab with a specific purpose then it should exist in it's own
directory and have full access to all the buildsets it needs.
Which means symlinks to those buildsets in buildset.controller.
If it's the former, I'll pull tonight. If it's the latter, please
resubmit this patch.
-b
> Note:In order to add a new distro as supported all the build sets
> should be PASS
>
> Signed-off-by: Monserrat Sedeno
> Signed-off-by: Aníbal Limón
> ---
> buildset-config.controller/nightly-qa-distro.conf | 55
> +++
> 1 file changed, 55 insertions(+)
> create mode 100644 buildset-config.controller/nightly-qa-distro.conf
>
> diff --git a/buildset-config.controller/nightly-qa-distro.conf
> b/buildset-config.controller/nightly-qa-distro.conf
> new file mode 100644
> index 000..def4118
> --- /dev/null
> +++ b/buildset-config.controller/nightly-qa-distro.conf
> @@ -0,0 +1,55 @@
> +[nightly-qa-distro]
> +builders: 'example-worker'
> +repos: [{'poky':
> +{'repourl':'git://git.yoctoproject.org/poky',
> + 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-
> bsp', 'yocto':'meta-yocto', 'poky':'meta-poky'},
> + 'branch':'master'}},
> +{'oecore':
> +{'repourl':'git://git.openembedded.org/openembedded-
> core',
> + 'layerversion':'core',
> + 'checkout':False,
> + 'branch':'master'}},
> +{'bitbake':
> +{'repourl':'git://git.openembedded.org/bitbake',
> + 'checkout':False,
> + 'branch':'master'}},
> +{'eclipse-poky-neon':
> +{'repourl':'git://git.yoctoproject.org/eclipse-poky',
> + 'checkout':False,
> + 'branch':'neon-master'}},
> +{'meta-qt4':
> +{'repourl':'git://git.yoctoproject.org/meta-qt4',
> + 'branch':'master'}},
> +{'meta-qt3':
> +{'repourl':'git://git.yoctoproject.org/meta-qt3',
> + 'branch':'master'}}]
> +props: [{'fp_date':{'prop_type':'StringParameter',
> + 'size': 20,
> + 'name': 'fp_date',
> + 'label':'Full Pass date:'}}]
> +steps: [{'SetDest':{}},
> +{'CheckOutLayers': {}},
> +{'RunPreamble': {}},
> +{'TriggerBuilds': {'schedulerName': 'dist-build',
> + 'waitForFinish': 'True',
> + 'schedulerNames': {
> + 'nightly-oe-selftest': {},
> + 'nightly-oecore': {},
> + 'nightly-deb': {},
> + 'nightly-ipk': {},
> + 'nightly-world': {},
> + 'nightly-arm': {},
> + 'nightly-multilib': {},
> + 'nightly-x86-64-lsb': {},
> + 'nightly-x86': {},
> + 'nightly-x32': {},
> + 'poky-tiny': {},
> + 'nightly-qa-systemd': {},
> + 'nightly-qa-extras': {},
> + 'nightly-qa-targetbuilds': {},
> + 'nightly-qa-skeleton': {},
> + 'nightly-qa-logrotate': {},
> + 'nightly-qa-pam': {},
> + 'buildtools': {}},
> + 'eclipse-plugin-neon': {},
> + 'schedulerNames_nowait': {}}},]
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [[yocto-autobuilder][PATCHv3]] Build sets to test new OS distribution in autobuilder
On Wed, 2016-10-05 at 15:54 -0500, Monserrat Sedeno wrote:
> As part of the process to set new OS distribution as supported on
> Yoctoc Project
> a new patch was created with the list of build sets that should be
> executed.
>
> Detailed information:
> https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan#Execute_Build_
> Sets
>
> Fixes [YOCTO #9905]
>
> Note:In order to add a new distro as supported all the build sets
> should be PASS
Sorry for the review delay here.
autobuilder-qa isn't really the right spot for this.
What I would suggest is:
1. A new directory called buildset-config.distro-qa
2. All targets needed for that buildset should be in there. If they
should track the buildsets in buildset-config.controller, make symlinks
so we don't need to maintain two sets of buildsets.
Everything in a buildset-config* should be self-contained and
buildable.
-b
>
> Signed-off-by: Monserrat Sedeno
> ---
> .../nightly-qa-distro.conf | 44
> ++
> 1 file changed, 44 insertions(+)
> create mode 100644 buildset-config.autobuilder-qa/nightly-qa-
> distro.conf
>
> diff --git a/buildset-config.autobuilder-qa/nightly-qa-distro.conf
> b/buildset-config.autobuilder-qa/nightly-qa-distro.conf
> new file mode 100644
> index 000..6c02a91
> --- /dev/null
> +++ b/buildset-config.autobuilder-qa/nightly-qa-distro.conf
> @@ -0,0 +1,44 @@
> +[nightly-qa-distro]
> +builders: 'example-worker'
> +repos: [{'poky':
> +{'repourl':'git://git.yoctoproject.org/poky',
> + 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-
> bsp', 'yocto':'meta-yocto', 'poky':'meta-poky'},
> + 'branch':'master'}},
> +{'meta-qt4':
> +{'repourl':'git://git.yoctoproject.org/meta-qt4',
> + 'branch':'master'}},
> +{'meta-qt3':
> +{'repourl':'git://git.yoctoproject.org/meta-qt3',
> + 'branch':'master'}}]
> +props: [{'fp_date':{'prop_type':'StringParameter',
> + 'size': 20,
> + 'name': 'fp_date',
> + 'label':'Full Pass date:'}}]
> +steps: [{'SetDest':{}},
> +{'CheckOutLayers': {}},
> +{'RunPreamble': {}},
> +{'TriggerBuilds': {'schedulerName': 'dist-build',
> + 'waitForFinish': 'True',
> + 'schedulerNames': {
> + 'nightly-oe-selftest': {},
> + 'nightly-rpm': {},
> + 'nightly-deb': {},
> + 'nightly-ipk': {},
> + 'nightly-world': {},
> + 'nightly-arm': {},
> + 'nightly-mips': {},
> + 'nightly-wic':{},
> + 'nightly-multilib': {},
> + 'nightly-x86-64': {},
> + 'nightly-x86-64-lsb': {},
> + 'nightly-x86': {},
> + 'poky-tiny': {},
> + 'nightly-qa-systemd': {},
> + 'nightly-qa-extras': {},
> + 'nightly-qa-targetbuilds': {},
> + 'nightly-qa-skeleton': {},
> + 'nightly-qa-logrotate': {},
> + 'nightly-qa-pam': {},
> + 'buildtools': {}},
> + 'schedulerNames_nowait': {}}},]
> +
> --
> 2.7.4
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto autobuilder][PATCH 0/3] Fix buildlogger
merged into master. Thanks! -b On Wed, 2016-09-07 at 16:33 +0100, Joshua Lock wrote: > Since build 999 we haven't seen any builds logged to the BuildLogs > wiki page, > that turns out to be because the JSON dicts keys are strings and thus > the sort > order isn't as expected, i.e. 999 > 1001. > > This series tidies up the buildlogger some and includes a fix for > this issue by > converting the keys of the dicts to a list of ints and sorting that > to determine > the most recent build. > > The following changes since commit > ba01fe19440a91091fe15544ecc2809a79f19401: > > nightly-qa-systemd.conf: Add create_eventlog property (2016-08-31 > 21:22:11 +0100) > > are available in the git repository at: > > git://git.yoctoproject.org/yocto-autobuilder joshuagl/buildlogger > http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/log/?h=joshu > agl/buildlogger > > Joshua Lock (3): > buildlogger: remove old, incomplete, comment > buildlogger: don't hardcode YP AB in generated URL > buildlogger: fix sorting of recent builds > > bin/buildlogger | 23 +-- > etc/buildlogger.conf.example | 1 + > 2 files changed, 14 insertions(+), 10 deletions(-) > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] nightly-wic.conf: add additional config settings for efi images
On Wed, 2016-08-24 at 10:40 -0700, Bill Randle wrote:
> Building efi disk images now requires extra config settings, so add
> IMAGE_FSTYPES and MACHINE_FEATURES appends to the auto.conf file.
>
> Signed-off-by: Bill Randle
>
Merged to master.
-b
> ---
> buildset-config.controller/nightly-wic.conf | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/buildset-config.controller/nightly-wic.conf b/buildset-
> config.controller/nightly-wic.conf
> index 1b91852..14e2411 100644
> --- a/buildset-config.controller/nightly-wic.conf
> +++ b/buildset-config.controller/nightly-wic.conf
> @@ -9,24 +9,24 @@ steps: [{'SetDest':{}},
> {'RunPreamble':{}},
> {'GetDistroVersion':{'distro': 'poky'}},
> {'CreateBBLayersConf':{'buildprovider':'yocto'}},
> -{'CreateAutoConf':{'machine':'qemux86'}},
> +{'CreateAutoConf':{'machine':'qemux86',
> 'atextappend':'\nIMAGE_FSTYPES += " hddimg"\nMACHINE_FEATURES_append
> = " efi"\n'}},
> {'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> {'BuildImages':{'images':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'mkefidisk',
> 'target_img':'core-image-sato'}},
> -{'CreateAutoConf':{'machine':'genericx86'}},
> +{'CreateAutoConf':{'machine':'genericx86',
> 'atextappend':'\nIMAGE_FSTYPES += " hddimg"\nMACHINE_FEATURES_append
> = " efi"\n'}},
> {'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> {'BuildImages':{'images':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'mkefidisk',
> 'target_img':'core-image-sato'}},
> -{'CreateAutoConf':{'machine':'qemux86-64'}},
> +{'CreateAutoConf':{'machine':'qemux86-64',
> 'atextappend':'\nIMAGE_FSTYPES += " hddimg"\nMACHINE_FEATURES_append
> = " efi"\n'}},
> {'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> {'BuildImages':{'images':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> -{'CreateAutoConf':{'machine':'genericx86-64'}},
> +{'CreateAutoConf':{'machine':'genericx86-64',
> 'atextappend':'\nIMAGE_FSTYPES += " hddimg"\nMACHINE_FEATURES_append
> = " efi"\n'}},
> {'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> {'BuildImages':{'images':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] nightly-musl.conf: add world build
Merged into master,
Thanks
-b
On Tue, 2016-08-09 at 10:34 -0700, Bill Randle wrote:
> Add world build for musl.
>
> [YOCTO #10105]
>
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly-musl.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/buildset-config.controller/nightly-musl.conf b/buildset-
> config.controller/nightly-musl.conf
> index 1f6aba5..cc2aea0 100644
> --- a/buildset-config.controller/nightly-musl.conf
> +++ b/buildset-config.controller/nightly-musl.conf
> @@ -12,7 +12,7 @@ steps: [{'SetDest':{}},
> 'buildhistory' : False, 'distro':
> 'poky',
> 'atextappend' : '\nTCLIBC="musl"\n' }},
> {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
> -{'BuildImages': {'images': 'core-image-minimal core-image-
> full-cmdline core-image-sato'}},
> +{'BuildImages': {'images': 'core-image-minimal core-image-
> full-cmdline core-image-sato world'}},
> {'DownloadErrorReports': {}},
> {'SendErrorReport': {}}]
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] SendQAEmail.py: use sendmail instead of mail to send QA email
Merged into master,
Thanks
-b
On Tue, 2016-08-09 at 09:42 -0700, Bill Randle wrote:
> When sending QA emails, the autobuilder uses the 'mail' command
> (typically
> installed as /usr/bin/mail or /bin/mail). However, most distributions
> do not
> install this program by default. They generally always install the
> 'sendmail'
> program, though, so use 'sendmail' as the mail agent, rather than
> 'mail'.
>
> [YOCTO #10082]
>
> Signed-off-by: Bill Randle
> ---
> .../autobuilder/buildsteps/SendQAEmail.py | 26
> --
> 1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/SendQAEmail.py b/lib/python2.7/site-
> packages/autobuilder/buildsteps/SendQAEmail.py
> index 0cd76d5..3691cc6 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/SendQAEmail.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/SendQAEmail.py
> @@ -47,9 +47,9 @@ class SendQAEmail(ShellCommand):
> properties = self.build.getProperties().asDict()
> repoprops = {}
> mailsubject = "Build available for QA"
> -email_header = '''
> -A build identified as needing QA has finished on the
> autobuilder. This
> -build is located at:\n\n
> +email_base = '''
> +A build identified as needing QA has finished on the autobuilder.
> This
> +build is located at:\n\n
> %s''' % (self.getProperty('DEST').replace(web_root, web_url))
>
> if str(self.getProperty("custom_release_me")) == "True":
> @@ -68,9 +68,9 @@ class SendQAEmail(ShellCommand):
> poky_number =
> self.getProperty("custom_poky_number")+prefix
> yocto_number =
> self.getProperty("custom_yocto_number")+prefix
> rel_name = 'yocto-'+ yocto_number
> -email_header = '''
> +email_base = '''
> A release candidate build for %s is now available at:\n\n
> -%s\n\n
> +%s\n\n
> Please begin QA on this build as soon as possible.''' % (rel_name,
> self.getProperty('DEST').replace(web_root, web_url))
> mailsubject = "Release Candidate Build for " +
> rel_name + snapshot + " now available."
>
> @@ -85,16 +85,18 @@ Please begin QA on this build as soon as
> possible.''' % (rel_name, self.getPrope
> for k, v in repoprops.iteritems():
> email_body = email_body + '%s : %s \n' % (k, v[1])
>
> -mailcmd = 'echo -e "' + email_header + '\n' + email_body
> + '\n' + mailsig + ' " | mail -s \'' + mailsubject + '\''
> -
> +email_header = ""
> +if mailto is not None and mailto is not "":
> +email_header += "To: " + mailto + "\n"
> if mailcc is not None and mailcc is not "":
> -mailcmd += " -c '" + mailcc + "' "
> -
> +email_header += "Cc: " + mailcc + "\n"
> if mailbcc is not None and mailbcc is not "":
> -mailcmd += " -b '" + mailbcc + "' "
> +email_header += "Bcc: " + mailbcc + "\n"
> +
> +email_header += "Subject: " + mailsubject + "\n"
> +
> +mailcmd = 'echo -e "' + email_header + "\n" + email_base
> + '\n' + email_body + '\n' + mailsig + ' " | sendmail -t'
>
> -if mailto is not None and mailto is not "":
> -mailcmd += " '" + mailto + "' "
> self.command = mailcmd
> else:
> self.command = 'echo "Not a QA build"'
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCHv2][yocto-autobuilder] lib/buildsteps.py: fix report creation in nigthly-oecore
On Fri, 2016-07-29 at 11:13 -0500, Aníbal Limón wrote:
> nightly-oecore buildset doesn't prove got_revision property
> so when got_revision is None use got_revision_oecore instead.
>
pulled into master, thanks!
-b
> [YOCTO #10051]
>
> Signed-off-by: Aníbal Limón
> ---
> lib/python2.7/site-packages/autobuilder/lib/buildsteps.py | 11
> +--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/lib/buildsteps.py b/lib/python2.7/site-
> packages/autobuilder/lib/buildsteps.py
> index eee0c1b..f7b1921 100644
> --- a/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py
> +++ b/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py
> @@ -118,8 +118,15 @@ class BitbakeShellCommand(ShellCommand):
> report['target_sys'] = vrs['TARGET_SYS']
>
> report['component'] = 'bitbake'
> -report['branch_commit'] = self.getProperty('branch') + ': '
> + \
> -self.getProperty('got_revision')
> +try:
> +branch = self.getProperty('branch')
> +revision = self.getProperty('got_revision')
> +if not revision:
> +revision = self.getProperty('got_revision_oecore')
> +except:
> +branch = "unknown_branch"
> +revision = "unknown_revision"
> +report['branch_commit'] = branch + ': ' + revision
>
> failure = {}
> failure['package'] = "bitbake-%s" % vrs['BB_VERSION']
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][yocto-autobuilder] lib/buildsteps.py: fix report creation in nigthly-oecore
On Fri, 2016-07-29 at 10:47 -0500, Aníbal Limón wrote: > > On 07/29/2016 10:31 AM, Beth 'pidge' Flanagan wrote: > > > > I'd put this in a try except. What happens with eclipse? > At this time we don't support eclipse, i'll add the try except and if > fails use "unknown_branch: unknown_revision". > > alimon > Ah, some of us still build for it! :D Remember, we try to not break stuff we still support. -b -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][yocto-autobuilder] lib/buildsteps.py: fix report creation in nigthly-oecore
On Fri, 2016-07-29 at 10:10 -0500, Aníbal Limón wrote:
> nightly-oecore buildset doesn't prove got_revision property
> so when got_revision is None use got_revision_oecore instead.
>
> [YOCTO #10051]
>
> Signed-off-by: Aníbal Limón
> ---
> lib/python2.7/site-packages/autobuilder/lib/buildsteps.py | 7 +-
> -
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/lib/buildsteps.py b/lib/python2.7/site-
> packages/autobuilder/lib/buildsteps.py
> index eee0c1b..37ac8b0 100644
> --- a/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py
> +++ b/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py
> @@ -118,8 +118,11 @@ class BitbakeShellCommand(ShellCommand):
> report['target_sys'] = vrs['TARGET_SYS']
>
> report['component'] = 'bitbake'
> -report['branch_commit'] = self.getProperty('branch') + ': '
> + \
> -self.getProperty('got_revision')
> +branch = self.getProperty('branch')
> +revision = self.getProperty('got_revision')
> +if not revision:
> +revision = self.getProperty('got_revision_oecore')
> +report['branch_commit'] = branch + ': ' + revision
>
I'd put this in a try except. What happens with eclipse?
-b
>
> failure = {}
> failure['package'] = "bitbake-%s" % vrs['BB_VERSION']
> --
> 2.1.4
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH 0/2] Allow OPTIMIZED_GIT_CLONE to be False
Merged into master -b On Sat, 2016-07-23 at 08:11 -0700, Bill Randle wrote: > The autobuilder code assumes OPTIMIZED_GIT_CLONE is always set True, > because things break if it is set to False. I had a case where it > needed to be set False because the git trash folder was on a > different > file system than the build directory. This caused the CheckOutLayers > build > step to fail. > > In addition, I still wanted to use the git mirror even with > OPTIMIZED_GIT_CLONE > set False, so allow that case, too. > > [YOCTO #10010] > > Bill Randle (2): > BuildSet.py: allow using local git mirror even if > OPTIMIZED_GIT_CLONE is False > yoctogit.py: ensure mirrordir is set before trying to use it > > lib/python2.7/site-packages/autobuilder/BuildSet.py| > 2 ++ > .../buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py | > 7 +-- > 2 files changed, 7 insertions(+), 2 deletions(-) > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH 0/2] Allow OPTIMIZED_GIT_CLONE to be False
On Sat, 2016-07-23 at 08:11 -0700, Bill Randle wrote: > The autobuilder code assumes OPTIMIZED_GIT_CLONE is always set True, > because things break if it is set to False. I had a case where it > needed to be set False because the git trash folder was on a > different > file system than the build directory. This caused the CheckOutLayers > build > step to fail. Part of me is tempted to just say "Don't Do That!" The plan was to eventually just use the optimized git clone, but if people are actually doing the above, then yes, this is needed. Let me review and then I'll push. -b > > In addition, I still wanted to use the git mirror even with > OPTIMIZED_GIT_CLONE > set False, so allow that case, too. > > [YOCTO #10010] > > Bill Randle (2): > BuildSet.py: allow using local git mirror even if > OPTIMIZED_GIT_CLONE is False > yoctogit.py: ensure mirrordir is set before trying to use it > > lib/python2.7/site-packages/autobuilder/BuildSet.py| > 2 ++ > .../buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py | > 7 +-- > 2 files changed, 7 insertions(+), 2 deletions(-) > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] nightly-wic.conf: build genericx86 wic images
Merged into master
-b
On Fri, 2016-07-22 at 10:35 -0700, Bill Randle wrote:
> QA requested wic images for genericx86, as well as x86-64 so include
> config and build for them.
>
> [YOCTO #10006]
>
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly-wic.conf | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/buildset-config.controller/nightly-wic.conf b/buildset-
> config.controller/nightly-wic.conf
> index 27584cb..47565ba 100644
> --- a/buildset-config.controller/nightly-wic.conf
> +++ b/buildset-config.controller/nightly-wic.conf
> @@ -9,6 +9,12 @@ steps: [{'SetDest':{}},
> {'RunPreamble':{}},
> {'GetDistroVersion':{'distro': 'poky'}},
> {'CreateBBLayersConf':{'buildprovider':'yocto'}},
> +{'CreateAutoConf':{'machine':'genericx86'}},
> +{'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> +{'BuildImages':{'images':'core-image-sato'}},
> +{'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> +{'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> +{'CreateWicImages':{'wic_img_type':'mkefidisk',
> 'target_img':'core-image-sato'}},
> {'CreateAutoConf':{'machine':'qemux86-64'}},
> {'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> {'BuildImages':{'images':'core-image-sato'}},
> @@ -20,5 +26,5 @@ steps: [{'SetDest':{}},
> {'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> {'CreateWicImages':{'wic_img_type':'mkefidisk',
> 'target_img':'core-image-sato'}},
> -{'PublishArtifacts': {'artifacts': ['qemux86-64',
> 'genericx86-64']}}]
> +{'PublishArtifacts': {'artifacts': ['qemux86-64',
> 'genericx86', 'genericx86-64']}}]
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH 0/4] autobuilder: make toaster eventlog creation optional
Merged into master. -b On Thu, 2016-07-14 at 10:05 -0700, Bill Randle wrote: > Currently, a toaster eventlog is generated for most all machine > specific > images (e.g., nightly-arm, nightly-x86, etc.) and placed in the top- > level > build directory. Having it in the top level dir causes inotify > overflow in > bitbake, due to the large number of changes to the file. > > This set of patches (1) make generation of the eventlog optional, by > having a user selection in the Forced Build web pages, (2) places the > eventlog in build/tmp/log, instead of build and (3) adds a timestamp > to > the eventlog filename since multiple event logs can be generated > during > a multi-image buildset and otherwise only the last one would > otherwise > be saved. > > [YOCTO #9884] > > Bill Randle (4): > remote_kick.py: add default entry for new 'create_eventlog' > property > BuildImages.py: build toaster eventlog only when requested > UploadToasterEventlog.py: handle multiple eventlog files > buildset-config.controller: add new 'create_eventlog' forced build > property > > bin/remote_kick.py | 1 + > buildset-config.controller/nightly-arm-lsb.conf| 4 > buildset-config.controller/nightly-arm.conf| 4 > buildset-config.controller/nightly-arm64.conf | 4 > buildset-config.controller/nightly-mips-lsb.conf | 4 > buildset-config.controller/nightly-mips.conf | 4 > buildset-config.controller/nightly-mips64.conf | 4 > buildset-config.controller/nightly-no-x11.conf | 4 > buildset-config.controller/nightly-ppc-lsb.conf| 4 > buildset-config.controller/nightly-ppc.conf| 4 > buildset-config.controller/nightly-x32.conf| 4 > buildset-config.controller/nightly-x86-64-lsb.conf | 4 > buildset-config.controller/nightly-x86-64.conf | 4 > buildset-config.controller/nightly-x86-lsb.conf| 4 > buildset-config.controller/nightly-x86.conf| 4 > buildset-config.controller/nightly.conf| 7 ++- > .../autobuilder/buildsteps/BuildImages.py | 24 > +++++----- > .../buildsteps/UploadToasterEventlog.py| 16 +++- > > 18 files changed, 93 insertions(+), 11 deletions(-) > -- Beth 'pidge' Flanagan toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [[yocto-autobuilder][PATCHv2] 00/15] Add support for generate bitbake/oe-selftest error reports
buildset-config.kernel/kernel-ppc-lsb.conf | 1 + > buildset-config.kernel/kernel-ppc.conf | 1 + > buildset-config.kernel/kernel-x86-64-lsb.conf | 1 + > buildset-config.kernel/kernel-x86-64.conf | 1 + > buildset-config.kernel/kernel-x86-lsb.conf | 1 + > buildset-config.kernel/kernel-x86.conf | 1 + > buildset-config.kernel/nightly-kernel.conf | 1 + > buildset-config.tizen/nightly-tizen-ivi.conf | 1 + > buildset-config.tizen/nightly-tizen.conf | 1 + > buildset-config.tizen/nightly.conf | 1 + > .../autobuilder/buildsteps/BuildImages.py | 7 +- > .../autobuilder/buildsteps/BuildToolchainImages.py | 7 +- > .../autobuilder/buildsteps/DownloadErrorReports.py | 42 + > .../autobuilder/buildsteps/GetBitbakeVersion.py| 6 +- > .../autobuilder/buildsteps/RunESDKSanityTests.py | 6 +- > .../autobuilder/buildsteps/RunOeSelftest.py| 46 + > .../autobuilder/buildsteps/RunSDKSanityTests.py| 6 +- > .../autobuilder/buildsteps/RunSanityTests.py | 6 +- > .../autobuilder/buildsteps/SendErrorReport.py | 16 ++-- > .../site-packages/autobuilder/lib/ABTools.py | 59 > > .../site-packages/autobuilder/lib/buildsteps.py| 104 > + > .../buildbot/steps/transfer.py | 86 > - > .../buildslave/commands/registry.py| 1 + > .../buildslave/commands/transfer.py| 79 > > 72 files changed, 509 insertions(+), 24 deletions(-) > create mode 100644 lib/python2.7/site- > packages/autobuilder/buildsteps/DownloadErrorReports.py > -- Beth 'pidge' Flanagan toganlabs.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [autobuilder][PATCH] nightly-arm.conf: build Cortex-A8 toolchains
Pulled into master, Thanks!
-b
On Fri, 2016-06-24 at 08:05 -0700, Bill Randle wrote:
> Since met-fsl-arm was dropped from the nightly builds, the Cortex-A8
> cross-
> compiler used for beaglebone builds is not created. Include toochain
> builds as part of nightly-arm now, so compiler is available for users
> of the beaglebone machine.
>
> [YOCTO #9810]
>
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly-arm.conf | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/buildset-config.controller/nightly-arm.conf b/buildset-
> config.controller/nightly-arm.conf
> index 76244ed..32920cf 100644
> --- a/buildset-config.controller/nightly-arm.conf
> +++ b/buildset-config.controller/nightly-arm.conf
> @@ -15,7 +15,11 @@ steps: [{'SetDest':{}},
> {'BuildImages': {'images': 'core-image-sato core-image-sato-
> dev core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
> {'RunSanityTests': {'images': 'core-image-minimal core-
> image-sato core-image-sato-sdk'}},
> {'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' :
> 'i686', 'distro': 'poky'}},
> +{'BuildToolchainImages': {}},
> {'BuildImages': {'images': 'core-image-sato core-image-sato-
> dev core-image-sato-sdk core-image-minimal core-image-minimal-dev
> core-image-sato-sdk-ptest'}},
> +{'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' :
> 'x86_64', 'distro': 'poky'}},
> +{'BuildToolchainImages': {}},
> +{'BuildImages': {'images': '-c populate_sdk_ext core-image-
> minimal'}},
> {'CreateAutoConf': {'machine': 'qemuarm', 'SDKMACHINE' :
> 'i686', 'distro': 'poky', 'buildhistory' : False}},
> {'BuildToolchainImages': {}},
> {'RunSDKSanityTests': {'images': 'core-image-sato'}},
--
Beth 'pidge' Flanagan
toganlabs.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [autobuilder][PATCH] CreateAutoConf.py: check for empty env history variables before using
Pulled into master, thanks!
On Thu, 2016-06-23 at 12:03 -0700, Bill Randle wrote:
> I saw this error on a new AB setup:
>
> File "/home/pokybuild/yocto-autobuilder/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py", line 181, in
> start
> ta_history_repos=ast.literal_eval(os.environ.get('BUILD_HISTORY_T
> HROWAWAY_WHITELIST').encode('utf-8'))
> exceptions.AttributeError: 'NoneType' object has no attribute
> 'encode'
>
> Since the code above line 181 checks for either
> BUILD_HISTORY_THROWAWAY_WHITELIST
> or BUILD_HISTORY_WHITELIST being set, it's possible one of them could
> be empty.
>
> Signed-off-by: Bill Randle
> ---
> .../site-packages/autobuilder/buildsteps/CreateAutoConf.py|
> 8 ++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> b/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> index 0845ff1..91607e6 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> @@ -177,9 +177,13 @@ class CreateAutoConf(ShellCommand):
>
> if os.environ.get('BUILD_HISTORY_WHITELIST') is not
> None or \
> os.environ.get('BUILD_HISTORY_THROWAWAY_WHITELIST
> ') is not None:
> +ta_history_repos={}
> +history_repos={}
> fout = fout + 'ERROR_QA_remove = "version-going-
> backwards"\n'
> -ta_history_repos=ast.literal_eval(os.environ.get
> ('BUILD_HISTORY_THROWAWAY_WHITELIST').encode('utf-8'))
> -history_repos=ast.literal_eval(os.environ.get('B
> UILD_HISTORY_WHITELIST').encode('utf-8'))
> +if
> os.environ.get('BUILD_HISTORY_THROWAWAY_WHITELIST') is not None:
> +ta_history_repos=ast.literal_eval(os.environ
> .get('BUILD_HISTORY_THROWAWAY_WHITELIST').encode('utf-8'))
> +if os.environ.get('BUILD_HISTORY_WHITELIST') is
> not None:
> + history_repos=ast.literal_eval(os.environ.ge
> t('BUILD_HISTORY_WHITELIST').encode('utf-8'))
> if repo in history_repos.keys() and \
> self.getProperty("branch") in
> history_repos[self.getProperty("repository")]:
> # We keep this build history
--
Beth 'pidge' Flanagan
toganlabs.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [[yocto-autobuilder][PATCHv2] 00/15] Add support for generate bitbake/oe-selftest error reports
On Thu, 2016-06-23 at 10:27 -0500, Aníbal Limón wrote:
>
> On 06/22/2016 03:17 PM, Aníbal Limón wrote:
> >
> >
> >
> > On 06/22/2016 02:44 AM, Beth 'pidge' Flanagan wrote:
> > >
> > > On Tue, 2016-06-21 at 18:07 -0500, Aníbal Limón wrote:
> > > >
> > > > This v2 adds support for generate also oe-selftest reports this
> > > > is
> > > > almost
> > > > the previous version with changes requested in review [1], the
> > > > next
> > > > patches
> > > > starts from patch,
> > > >
> > > > autobuilder/lib/{ABtools,builsteps}.py: Create
> > > > save_error_report func
> > > A few comments.
> > >
> > > - Please rebase the last two commits. They can be merged into
> > > prior
> > > commits.
> > >
> > > Example: 0eb495d93eefa9ead8f4b1242f251f1a2288db68 should be
> > > squashed
> > > into 83b6707622128436b4ece9d4c2a89311b000c209
> > >
> > > We shouldn't need rename commits for a pull request that created
> > > the
> > > original thing we're renaming.
> > >
> > > - Please fix the title for
> > > 83b6707622128436b4ece9d4c2a89311b000c209
> > > 's/buiidsets/buildsets/'
> > I squashed the changes now at,
> >
> > http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log/?h=
> > contrib/alimon/devel2
> >
> > alimon
> Hi,
>
> The Error report web needed changes are now integrated [1], if you
> ack'ed the changes we could proceed to integrate/deploy these changes
> to
> enable send Bitbake/OE-seltest errors to ERW.
>
> [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7583#c14
>
> Cheers,
> alimon
Let me review them tonight and if they're ok, I'll pull them into
master.
-b
>
> >
> > >
> > >
> > >
> > > -b
> > >
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCHv2] nightly-world-lsb.conf: skip Publish step so artifacts don't overwrite nightly-world ones
Pulled into master, thanks!
-b
On Tue, 2016-06-21 at 07:38 -0700, Bill Randle wrote:
> Signed-off-by: Bill Randle
> ---
> v2: delete line, rather than commenting it out
>
> buildset-config.controller/nightly-world-lsb.conf | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/buildset-config.controller/nightly-world-lsb.conf
> b/buildset-config.controller/nightly-world-lsb.conf
> index 4c9994c..472a714 100644
> --- a/buildset-config.controller/nightly-world-lsb.conf
> +++ b/buildset-config.controller/nightly-world-lsb.conf
> @@ -21,6 +21,5 @@ steps: [{'SetDest':{}},
> 'distro': 'poky-lsb'}},
> {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
> {'BuildImages': {'images': 'world'}},
> -{'SendErrorReport': {}},
> -{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
> +{'SendErrorReport': {}}]
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [[yocto-autobuilder][PATCHv2] 00/15] Add support for generate bitbake/oe-selftest error reports
On Tue, 2016-06-21 at 18:07 -0500, Aníbal Limón wrote:
> This v2 adds support for generate also oe-selftest reports this is
> almost
> the previous version with changes requested in review [1], the next
> patches
> starts from patch,
>
> autobuilder/lib/{ABtools,builsteps}.py: Create
> save_error_report func
A few comments.
- Please rebase the last two commits. They can be merged into prior
commits.
Example: 0eb495d93eefa9ead8f4b1242f251f1a2288db68 should be squashed
into 83b6707622128436b4ece9d4c2a89311b000c209
We shouldn't need rename commits for a pull request that created the
original thing we're renaming.
- Please fix the title for 83b6707622128436b4ece9d4c2a89311b000c209
's/buiidsets/buildsets/'
-b
--
Beth 'pidge' Flanagan
toganlabs.com
>
> Also the changes could be reviewed at [2].
>
> [1] https://lists.yoctoproject.org/pipermail/yocto/2016-June/030515.h
> tml
> [2] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log/?
> h=contrib/alimon/devel
>
> Aníbal Limón (15):
> lib/buildsteps.py: Add BitbakeShellCommand class
> lib/buildsteps.py: Add BitbakeLogLineObserver for
> BitbakeShellCommands.
> lib/buildsteps: BitbakeShellCommand add support for create error
> reports
> lib/ABTools: Add functions for get errordir path in controller and
> worker
> buildbot: Add support for DirectoryDownload transfer step
> autobuilder/buildsteps: Add DownloadBitbakeErrorReports step
> buiidsets: Add DownloadBitbakeErrorReport step
> lib/buildsteps.py: BitbakeShellCommand add support for error_type
> autobuilder/lib/buildsteps.py: BitbakeShellCommand update error
> report
> types.
> autobuilder/lib/{ABtools,builsteps}.py: Create save_error_report
> func
> autobuilder/lib/ABTools.py: Add get_lsb_distro function
> buildsteps/RunOeSelftest.py: Add support for create/save error
> reports
> nightly-oe-selftest.conf: Add steps for Download and Send error
> report.
> autobuilder/buildsteps: Rename DownloadBitbakeErrorReports to
> DownloadErrorReports
> buildset-config: Update references from DownloadBitbakeErrorReports
> to
> DownloadErrorReports
>
> buildset-config.controller/build-appliance.conf| 1 +
> buildset-config.controller/buildtools.conf | 1 +
> buildset-config.controller/nightly-arm-lsb.conf| 1 +
> buildset-config.controller/nightly-arm.conf| 1 +
> buildset-config.controller/nightly-arm64.conf | 1 +
> .../nightly-deb-non-deb.conf | 1 +
> buildset-config.controller/nightly-deb.conf| 1 +
> buildset-config.controller/nightly-ipk.conf| 1 +
> buildset-config.controller/nightly-mips-lsb.conf | 1 +
> buildset-config.controller/nightly-mips.conf | 1 +
> buildset-config.controller/nightly-mips64.conf | 1 +
> buildset-config.controller/nightly-multilib.conf | 1 +
> buildset-config.controller/nightly-musl.conf | 1 +
> buildset-config.controller/nightly-no-x11.conf | 1 +
> buildset-config.controller/nightly-non-gpl3.conf | 1 +
> .../nightly-oe-selftest.conf | 5 +-
> buildset-config.controller/nightly-oecore.conf | 1 +
> buildset-config.controller/nightly-ppc-lsb.conf| 1 +
> buildset-config.controller/nightly-ppc.conf| 1 +
> buildset-config.controller/nightly-qa-extras.conf | 1 +
> .../nightly-qa-logrotate.conf | 1 +
> buildset-config.controller/nightly-qa-pam.conf | 1 +
> .../nightly-qa-skeleton.conf | 1 +
> buildset-config.controller/nightly-qa-systemd.conf | 1 +
> .../nightly-qa-targetbuilds.conf | 1 +
> .../nightly-rpm-non-rpm.conf | 1 +
> buildset-config.controller/nightly-rpm.conf| 1 +
> buildset-config.controller/nightly-uclibc.conf | 1 +
> buildset-config.controller/nightly-world-lsb.conf | 1 +
> buildset-config.controller/nightly-world.conf | 1 +
> buildset-config.controller/nightly-x32.conf| 1 +
> buildset-config.controller/nightly-x86-64-lsb.conf | 1 +
> buildset-config.controller/nightly-x86-64.conf | 1 +
> buildset-config.controller/nightly-x86-lsb.conf| 1 +
> buildset-config.controller/nightly-x86.conf| 1 +
> buildset-config.controller/nightly.conf| 1 +
> buildset-config.controller/poky-tiny.conf | 1 +
> buildset-config.examples/awesomefirmware.conf | 1 +
> buildset-config.freescale/nightly-fsl-arm-lsb.conf | 1 +
> buildset-config.freescale/nightly-fsl-arm.conf | 1 +
> buildset-config.freescale/nightly-fsl-ppc-lsb.conf | 1 +
>
Re: [yocto] [yocto-autobuilder][PATCH] nightly-world-lsb.conf: skip Publish step so artifacts don't overwrite nightly-world ones
On Mon, 2016-06-20 at 08:00 -0700, Bill Randle wrote:
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly-world-lsb.conf | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/buildset-config.controller/nightly-world-lsb.conf
> b/buildset-config.controller/nightly-world-lsb.conf
> index 4c9994c..f755920 100644
> --- a/buildset-config.controller/nightly-world-lsb.conf
> +++ b/buildset-config.controller/nightly-world-lsb.conf
> @@ -21,6 +21,7 @@ steps: [{'SetDest':{}},
> 'distro': 'poky-lsb'}},
> {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
> {'BuildImages': {'images': 'world'}},
> -{'SendErrorReport': {}},
> -{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
> +{'SendErrorReport': {}}]
> +# skip Publish step so artifacts don't overwrite nightly-world ones
> +# {'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
>
It would be best here to just remove the lines rather than comment them
out. Please resubmit with the lines removed.
> --
> 2.5.5
>
--
Beth 'pidge' Flanagan
toganlabs.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][yocto-autobuilder] autobuilder/Autobuilder.p: Add missing import of buildbot.util.
On Fri, 2016-06-17 at 11:05 -0500, Aníbal Limón wrote: > When try to start Autobuilder fails with the next exception, > > 2016-06-07 17:06:45-0500 [-] LOADING CONFIG FILE > 2016-06-07 17:06:45-0500 [-] error while parsing config file: > > Traceback (most recent call last): > File > "/home/alimon/repos/yocto-autobuilder/lib/python2.7/site- > packages/Twisted-12.2.0-py2.7-linux- > x86_64.egg/twisted/internet/defer.py", > line 551, in _runCallbacks > .. > .. > .. > File > "/home/alimon/repos/yocto-autobuilder/lib/python2.7/site- > packages/autobuilder/Autobuilder.py", > line 54, in createBuildsets > util.naturalSort(buildersSorted) > exceptions.NameError: global name 'util' is not defined > > Signed-off-by: Aníbal Limón Pulled into master. I'm going to have a few patches today to pull in. One from Bill Randle, and if you have the rebase done for our bitbakeshell branch, that as well, so we might want to consider getting production updated. Have we run your BitbakeShell branch of the devel cluster (or any cluster not on a single machine, which is generally where we find issues) yet? -b > --- > lib/python2.7/site-packages/autobuilder/Autobuilder.py | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/lib/python2.7/site-packages/autobuilder/Autobuilder.py > b/lib/python2.7/site-packages/autobuilder/Autobuilder.py > index 6c3e578..23f0a74 100644 > --- a/lib/python2.7/site-packages/autobuilder/Autobuilder.py > +++ b/lib/python2.7/site-packages/autobuilder/Autobuilder.py > @@ -19,6 +19,7 @@ from buildbot.schedulers.basic import > SingleBranchScheduler > from buildbot.changes import filter > from buildbot.changes.pb import PBChangeSource > from buildbot.changes.gitpoller import * > +from buildbot import util > from lib.ABTools import capitalize > import ast > import BuildSet -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder] [RFC] Add support for generate bitbake error reports
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 > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder] [RFC] Add support for generate bitbake error reports
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) 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 -- Beth 'pidge' Flanagan toganlabs.com > Cheers, > alimon > > [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7583 > [2] > http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log/?h=co > ntrib/alimon/devel > [3] > http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/lib/ > python2.7/site- > packages/autobuilder/lib/buildsteps.py?h=contrib/alimon/devel#n92 > [4] > http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/lib/ > python2.7/site- > packages/autobuilder/lib/buildsteps.py?h=contrib/alimon/devel#n53 > [5] > http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?h > =contrib/alimon/devel&id=4022920bb0e56d1eef3dfe7c5e9b4699f801cdf1 > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
