Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-27 Thread Bruce Ashfield
On Thu, Apr 27, 2017 at 12:32 PM, Martin Jansa wrote: > Yesterday I've deleted all workspaces where I was getting this error and > since then I haven't seen one. > > So maybe the key to reproduce this was to run builds without the fix > applied and then apply the fix and

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-27 Thread Martin Jansa
Yesterday I've deleted all workspaces where I was getting this error and since then I haven't seen one. So maybe the key to reproduce this was to run builds without the fix applied and then apply the fix and execute another build without removing the tmp-glibc (so that it tries to do incremental

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-26 Thread Bruce Ashfield
On Wed, Apr 26, 2017 at 8:25 AM, Burton, Ross wrote: > Not sure if it's related to this problem, but this happened in selftest > last night: > > Log data follows: > | DEBUG: Executing shell function do_kernel_metadata > | ERROR: Could not generate configuration queue for

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-26 Thread Burton, Ross
Not sure if it's related to this problem, but this happened in selftest last night: Log data follows: | DEBUG: Executing shell function do_kernel_metadata | ERROR: Could not generate configuration queue for qemux86. |

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-25 Thread Bruce Ashfield
On Tue, Apr 25, 2017 at 9:09 AM, Richard Purdie wrote: > On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote: > > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie > > wrote: > > > On Mon, 2017-04-24 at 15:56 -0400,

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-25 Thread Richard Purdie
On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote: > On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie > wrote: > > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Bruce Ashfield
On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield > .com> wrote: > > > > > > > > > On Mon, Apr 24, 2017 at 9:39

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Richard Purdie
On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote: > > > On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield .com> wrote: > > > > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > om> wrote: > > > I'm still seeing this with your

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Bruce Ashfield
On Mon, Apr 24, 2017 at 4:05 PM, Martin Jansa wrote: > > There's some incantation or config that I'm missing, I assume this is a > straight qemux86 config > with a bitbake of something like core-image-minimal ? > > One of the layers has linux-yocto_4.10.bbappend with 4

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Martin Jansa
> There's some incantation or config that I'm missing, I assume this is a straight qemux86 config with a bitbake of something like core-image-minimal ? One of the layers has linux-yocto_4.10.bbappend with 4 added .cfg files and one .patch file. Maybe that could influence do_patch behavior. On

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Bruce Ashfield
On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield wrote: > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa > wrote: > >> I'm still seeing this with your "kernel-yocto/kern-tools: fix >> do_validate_branches clean stage" patch applied: >> >> >> |

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Bruce Ashfield
On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa wrote: > I'm still seeing this with your "kernel-yocto/kern-tools: fix > do_validate_branches clean stage" patch applied: > > > | DEBUG: Executing shell function do_patch > | ERROR: Could not apply patches for qemux86. > |

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-24 Thread Martin Jansa
I'm still seeing this with your "kernel-yocto/kern-tools: fix do_validate_branches clean stage" patch applied: | DEBUG: Executing shell function do_patch | ERROR: Could not apply patches for qemux86. | ERROR: Patch failures can be resolved in the linux source directory

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Bruce Ashfield
On Fri, Apr 21, 2017 at 3:47 PM, Bruce Ashfield wrote: > > > On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield > wrote: > >> >> >> On Fri, Apr 21, 2017 at 11:55 AM, akuster808 >> wrote: >> >>> >>> >>> On 04/21/2017 01:36

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Bruce Ashfield
On Fri, Apr 21, 2017 at 1:50 PM, Bruce Ashfield wrote: > > > On Fri, Apr 21, 2017 at 11:55 AM, akuster808 wrote: > >> >> >> On 04/21/2017 01:36 AM, Martin Jansa wrote: >> >> Anyone else seeing this as well? >> >> >> yes >> > > If you see it, can

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Bruce Ashfield
On Fri, Apr 21, 2017 at 11:55 AM, akuster808 wrote: > > > On 04/21/2017 01:36 AM, Martin Jansa wrote: > > Anyone else seeing this as well? > > > yes > If you see it, can you take a look at the linux source dir and see if the directories are present ? I've been doing a

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread akuster808
On 04/21/2017 01:36 AM, Martin Jansa wrote: Anyone else seeing this as well? yes - armin I've updated to oe-core commit: c6cd5865b6914521a841ae0c9f4e2bcda99beff2 from some revision maybe 20-40 commits older and now I'm seeing: ERROR: linux-yocto-1_4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Bruce Ashfield
On Fri, Apr 21, 2017 at 9:44 AM, Martin Jansa wrote: > On Fri, Apr 21, 2017 at 08:39:33AM -0400, Bruce Ashfield wrote: > > On Fri, Apr 21, 2017 at 8:36 AM, Alexander Kanavin < > > alexander.kana...@linux.intel.com> wrote: > > > > > On 04/21/2017 03:26 PM, Bruce Ashfield

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Martin Jansa
On Fri, Apr 21, 2017 at 08:39:33AM -0400, Bruce Ashfield wrote: > On Fri, Apr 21, 2017 at 8:36 AM, Alexander Kanavin < > alexander.kana...@linux.intel.com> wrote: > > > On 04/21/2017 03:26 PM, Bruce Ashfield wrote: > > > > Anyone else seeing this as well? > >> > >> > >> > >> Richard saw this

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Bruce Ashfield
On Fri, Apr 21, 2017 at 8:36 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 04/21/2017 03:26 PM, Bruce Ashfield wrote: > > Anyone else seeing this as well? >> >> >> >> Richard saw this once last week, and we weren't able to reproduce it. >> I've just updated >> and am

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Alexander Kanavin
On 04/21/2017 03:26 PM, Bruce Ashfield wrote: Anyone else seeing this as well? Richard saw this once last week, and we weren't able to reproduce it. I've just updated and am doing builds now. If anyone has info on their config, build steps, etc, I'm interested to hear so I can figure

Re: [OE-core] linux-yocto.do_validate_branches failing since last oe-core update

2017-04-21 Thread Bruce Ashfield
On Fri, Apr 21, 2017 at 4:36 AM, Martin Jansa wrote: > Anyone else seeing this as well? > > > Richard saw this once last week, and we weren't able to reproduce it. I've just updated and am doing builds now. If anyone has info on their config, build steps, etc, I'm