Re: [yocto] [[PATCH][yocto-autobuilder]] bin/forcebuild.py: Add a script to support force a build

2017-02-15 Thread Lock, Joshua G
On Wed, 2017-02-08 at 09:10 -0600, Aníbal Limón wrote: > > On 02/08/2017 08:12 AM, Lock, Joshua G wrote: > > On Wed, 2017-02-01 at 14:14 -0600, Aníbal Limón wrote: > > > I know we have the remote_kick.py [1] script but i don't know if > > > is > > > c

Re: [yocto] [[PATCH][yocto-autobuilder]] bin/forcebuild.py: Add a script to support force a build

2017-02-08 Thread Lock, Joshua G
On Wed, 2017-02-01 at 14:14 -0600, Aníbal Limón wrote: > I know we have the remote_kick.py [1] script but i don't know if is > currently on use also this new script support list the options in > builders and specify custom ones via cmdline. I don't use remote_kick.py, I'm loathe to carry two scrip

[yocto] SWAT Reboot

2016-11-15 Thread Lock, Joshua G
The short version is that the SWAT process document has been updated, if you're a member of the SWAT team please take a few moments to read this mail and update the wiki. We're making a concerted effort in the 2.3 cycle to improve the SWAT process and ensure that it's operating effectively. To t

Re: [yocto] Migration info - runqemu

2016-10-19 Thread Lock, Joshua G
: On 10/14/2016 04:35 PM, Lock, Joshua G wrote: On Fri, 2016-10-14 at 10:12 +0800, Robert Yang wrote: Hi Paul and Scott, Here it is, and please feel free to comment, most of them are from qemuboot.bbclass: The new runqemu is a python script, it requires a -.qemuboot.conf to boot the bsp, the qem

Re: [yocto] Migration info - runqemu

2016-10-14 Thread Lock, Joshua G
On Fri, 2016-10-14 at 10:12 +0800, Robert Yang wrote: > Hi Paul and Scott, > > Here it is, and please feel free to comment, most of them are from > qemuboot.bbclass: > > The new runqemu is a python script, it requires a > -.qemuboot.conf to boot the bsp, the > qemuboot.conf > is generated by qemu

Re: [yocto] [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests

2016-10-13 Thread Lock, Joshua G
Can you help me understand why you needed to create this patch? We've run into some issues recently where toolchains we expected to be built weren't and the PublishArtifacts buildstep failing because they're missing is useful. With this change we'll no longer get that, right? Thanks, Joshua

Re: [yocto] Release Candidate Build for yocto-2.2.rc1.rc1 now available.

2016-10-13 Thread Lock, Joshua G
On Thu, 2016-10-13 at 15:36 +, Poky Build User wrote: > A release candidate build for yocto-2.2.rc1 is now available at: > > > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc1 > > > Please begin QA on this build as soon as possible. Please don't, this build isn't ready fo

Re: [yocto] Release Candidate Build for yocto-2.2.rc1.rc1 now available.

2016-10-12 Thread Lock, Joshua G
On Wed, 2016-10-12 at 08:07 +, Poky Build User wrote: > A release candidate build for yocto-2.2.rc1 is now available at: > > > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc1 > > > Please begin QA on this build as soon as possible. This isn't a useful QA target a

Re: [yocto] Release Candidate Build for yocto-2.2.rc1.rc1 now available.

2016-10-12 Thread Lock, Joshua G
On Wed, 2016-10-12 at 08:07 +, Poky Build User wrote: > A release candidate build for yocto-2.2.rc1 is now available at: > > > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2.rc1 > > > Please begin QA on this build as soon as possible. This isn't a useful QA target as not ev

Re: [yocto] [meta-swupd][PATCH] swupdimage.bbclass: ensure that do_rootfs gets executed

2016-09-12 Thread Lock, Joshua G
On Mon, 2016-09-12 at 09:09 +0200, Patrick Ohly wrote: > OE-core commit 6d969bacc718e changed do_rootfs so that it creates > IMGDEPLOYDIR. That change broke the creation of additional swupd > images, because setting do_rootfs to empty caused the entire task to > be skipped, including the evaluation