From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mail.openembedded.org (Postfix) with ESMTP id 49B2673755 for ; Wed, 6 May 2015 22:49:49 +0000 (UTC) Received: by widdi4 with SMTP id di4so39262260wid.0 for ; Wed, 06 May 2015 15:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zHJrF4Schdot36H/0vIiLRxWCpMhZK3Eo2eS3Z53NDk=; b=JVuU40vv/2QW3so9F+hh/w0Qw6RbhcgD/zyYsVEtlD3i9mXFhqwZs8SjemXIevBOq8 Rp4iah7GFpwhKaW7onQMnA8EO2abqGkYjir8Jl8BSvsCTipolMLn6YVliEep4ogAYdqo 3Qoy3hZ7aoxLQz15rViDkS1q70D5kwvVbPd8I+jurFq2Ly4laDCz8m+sJj3cOcjnFhx1 bSmRlO1QcVdRzTLWE6FktlyetlvyRYPdBYLDKdf3DQgRFJl4Yru8bNPyPwbwWQGMrJWd nAVLOMB98YxKPqq7Rs1avzD2Y40z4f2LONoNyAN+SF2Kxe2RpBg6yTNJg9MKSeskYdWf Tg0A== MIME-Version: 1.0 X-Received: by 10.194.57.109 with SMTP id h13mr1615323wjq.67.1430952590483; Wed, 06 May 2015 15:49:50 -0700 (PDT) Received: by 10.28.157.193 with HTTP; Wed, 6 May 2015 15:49:50 -0700 (PDT) In-Reply-To: <1430947966.8074.108.camel@linuxfoundation.org> References: <1430521154.18360.28.camel@linuxfoundation.org> <55440C90.5060605@windriver.com> <20150502081346.GD2366@jama> <55458D0D.6070904@windriver.com> <20150506144241.GA2067@jama> <554A2C1C.5040304@windriver.com> <20150506153325.GB2067@jama> <1430927086.8074.65.camel@linuxfoundation.org> <20150506160708.GD2067@jama> <554A536C.5060608@windriver.com> <1430947966.8074.108.camel@linuxfoundation.org> Date: Thu, 7 May 2015 00:49:50 +0200 Message-ID: From: Martin Jansa To: Richard Purdie Cc: Patches and discussions about the oe-core layer Subject: Re: [PATCH 0/5] linux-yocto: consolidated pull request X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 22:49:50 -0000 Content-Type: multipart/alternative; boundary=047d7ba96ef0d8a7b60515719c30 --047d7ba96ef0d8a7b60515719c30 Content-Type: text/plain; charset=UTF-8 I use tmpfs in most of my builds, so in most cases when I see the error from the build, tmpfs is already gone (purged by next build executed on the same sever). On Wed, May 6, 2015 at 11:32 PM, Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote: > > On 2015-05-06 12:07 PM, Martin Jansa wrote: > > > I've used master-next week or two ago (mostly to test bluez4 and > python3 > > > changes) and soon after that dropped all linux-yocto related changes > > > from it assuming that it's indeed cause for the issues I'm seeing, but > > > it's not and it's still failing with master as well (and my > > > jenkins/world builds are just small portion of my builds executed > > > elsewhere where I see similar issues). > > > > Richard: How can we sort out the differences between the build > > environment that Martin uses versus what the autobuilder is showing? > > > > There's nothing particularly complex happening during that build, > > it's a checkout and generation of a config. > > > > I'm unable to reproduce any of the failures, and neither is the > > autobuilder. > > This is a tough one and I'm struggling a little. We could try looking at > the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in > particular) as well as > tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order > > Martin, would you be able to share the above somewhere? I'm hoping this > would give us a clue as to what the difference is between the builds and > allow us to reproduce the problem. > > Cheers, > > Richard > > > --047d7ba96ef0d8a7b60515719c30 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I use tmpfs in most of my builds, so in most cases when I = see the error from the build, tmpfs is already gone (purged by next build e= xecuted on the same sever).

On Wed, May 6, 2015 at 11:32 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
On Wed, 2015-05-06 at 13:46 -0= 400, Bruce Ashfield wrote:
> On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > I've used master-next week or two ago= (mostly to test bluez4 and python3
> > changes) and soon after that dropped all linux-yocto related chan= ges
> > from it assuming that it's indeed cause for the issues I'= m seeing, but
> > it's not and it's still failing with master as well (and = my
> > jenkins/world builds are just small portion of my builds executed=
> > elsewhere where I see similar issues).
>
> Richard: How can we sort out the differences between the build
> environment that Martin uses versus what the autobuilder is showing? >
> There's nothing particularly complex happening during that build,<= br> > it's a checkout and generation of a config.
>
> I'm unable to reproduce any of the failures, and neither is the > autobuilder.

This is a tough one and I'm struggling a little. We could try lo= oking at
the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
particular) as well as
tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order

Martin, would you be able to share the above somewhere? I'm hoping this=
would give us a clue as to what the difference is between the builds and allow us to reproduce the problem.

Cheers,

Richard



--047d7ba96ef0d8a7b60515719c30--