All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: linux-yocto.do_validate_branches failing since last oe-core update
Date: Tue, 25 Apr 2017 14:09:40 +0100	[thread overview]
Message-ID: <1493125780.19076.132.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4M1m5RLNXyRjyyybD+jNzZbQqkrW+SDtjHu3dP28rb-aA@mail.gmail.com>

On Mon, 2017-04-24 at 21:06 -0400, Bruce Ashfield wrote:
> On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie
> <richard.purdie@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 <bruce.ashfield@g
> > mail
> > > .com> wrote:
> > > >
> > > >
> > > > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa <martin.jansa@gma
> > il.c
> > > > om> wrote:
> > 
> > >
> > > Richard/Ross: are you seeing this same thing on the autobuilder ?
> > >
> > > 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 ?
> > 
> > We're not seeing this on the autobuilders. I do suspect something
> > in
> > the handling of extra patches or cfg fragments from SRC_URI if I
> > had to
> > guess. That certainly was the trigger last time I saw this.
> Yah, that's the kicker, I'm still carrying your patch for binfmt_elf,
> and I added two of my own
> + config fragments, and I can't trigger anything.

I managed to reproduce breakage. With master and my separate patch in
SRC_URI:

$ bitbake linux-yocto
$ bitbake linux-yocto -c kernel_checkout -f
$ bitbake linux-yocto

ERROR: linux-yocto-4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0 do_validate_branches: Function failed: do_validate_branches (log file is located at /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726)
ERROR: Logfile of failure stored in: /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726
Log data follows:
| DEBUG: Executing shell function do_validate_branches
| HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base
| 1493125671.284715: mkdir: cannot create directory ‘.’: File exists
| 1493125671.370592:
| 1493125671.3742917: [ERROR] Can't find patch dir at ./patches/standard/base
| 1493125671.3742917: usage: kgit s2q
| 1493125671.3743172: WARNING: exit code 1 from a shell command.
| 1493125671.3745801: ERROR: Function failed: do_validate_branches (log file is located at /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/linux-yocto/4.10.9+gitAUTOINC+ad2e885015_fe0fb8da3d-r0/temp/log.do_validate_branches.116726)

Cheers,

Richard





  reply	other threads:[~2017-04-25 13:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  8:36 linux-yocto.do_validate_branches failing since last oe-core update Martin Jansa
2017-04-21 12:26 ` Bruce Ashfield
2017-04-21 12:36   ` Alexander Kanavin
2017-04-21 12:39     ` Bruce Ashfield
2017-04-21 13:44       ` Martin Jansa
2017-04-21 13:48         ` Bruce Ashfield
2017-04-21 15:55 ` akuster808
2017-04-21 17:50   ` Bruce Ashfield
2017-04-21 19:47     ` Bruce Ashfield
2017-04-22  4:39       ` Bruce Ashfield
2017-04-24 13:39         ` Martin Jansa
2017-04-24 13:54           ` Bruce Ashfield
2017-04-24 19:56             ` Bruce Ashfield
2017-04-24 20:05               ` Martin Jansa
2017-04-24 20:13                 ` Bruce Ashfield
2017-04-24 21:27               ` Richard Purdie
2017-04-25  1:06                 ` Bruce Ashfield
2017-04-25 13:09                   ` Richard Purdie [this message]
2017-04-25 13:17                     ` Bruce Ashfield
2017-04-26 12:25                       ` Burton, Ross
2017-04-26 12:45                         ` Bruce Ashfield
2017-04-27 16:32                           ` Martin Jansa
2017-04-27 18:46                             ` Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1493125780.19076.132.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.