All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
	"Yan, Xiaofeng" <Xiaofeng.Yan@windriver.com>,
	Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: 3 Failures in RC3
Date: Sun, 07 Aug 2011 13:09:04 -0700	[thread overview]
Message-ID: <4E3EF0E0.5000107@linux.intel.com> (raw)
In-Reply-To: <CAPhnLPBYMtEy-ny0Yo+QMHWU7chbk2zj4xG-rC1gqpGYMASTqA@mail.gmail.com>

On 08/07/2011 11:11 AM, Flanagan, Elizabeth wrote:
> On Sat, Aug 6, 2011 at 4:20 PM, Saul Wold<sgw@linux.intel.com>  wrote:
>> On 08/06/2011 11:23 AM, Saul Wold wrote:
>>>
>>> Folks,
>>>
>>> We currently have 3 failures on the RC3 build for M3. They are all
>>> related to LSB builds. If you are on the TO: line please review your
>>> issues as we need a prompt fix.
>>>
>>> 1348: Qt3 Fails to build for ARM LSB
>>>
>>> 1349: Shared State Information gets lost for Mips FSTests
>>> I am trying to reproduce this on the Autobuilder
>>>
>> I am still working on reproducing this one, might be autobuilder related as
>> my local autobuilder build seems to be OK right now.
>> I have 2 sets of sstate for fstests, which may mean that something is
>> different between the poky and poky-lsb builds.
>>
>> On the autobuilder, the sstate directory was empty, so I can't verify
>> short of restarting the build again.
>
> Look at http://autobuilder.yoctoproject.org/nightly/CURRENT/sstate-cache
>
> That is the saved sstate for that build.
>
I found the correct location in the autobuilder, but it seems that the 
sstate-cache is bad and should be removed, I thought we where removing 
sstate before starting a nightly?

The bad sets are:
sstate-fstests-mips-poky-linux-0.0+svnr426-r1-mips-2-1ac2de42c742acfe5b35e44bfe68e7c1_package.*
sstate-fstests-mips-poky-linux-0.0+svnr426-r1-mips-2-44cb8fcc9b29e00d9d339e641c333d1e_package.*

sstate-fstests-mips-poky-linux-0.0+svnr426-r1-mips-2-ad481871e7622c756a3262632dfb088c_deploy-rpm.*
sstate-fstests-mips-poky-linux-0.0+svnr426-r1-mips-2-79fefc65e6e34db9ae3bfbfdff6f9522_deploy-rpm.*

I think if those are removed or the sstate is reset for each nightly 
build the fstest issue will go away.

>>
>>> 1450: ccache directory does not get created correct
>>
>> oops 1350 is the correct bugid!
>>
>>> I can reproduce this one very easily by building, saving the
>>> sstate-cache directory and then building again with a clean tmp
>>> directory. The ccache/x86-64-poky-linux directory does not get created
>>> and the kernel-configme task fail during the HOSTCC execution.
>>>
>> I have a fix for this one, in MUT and oe-contrib/sgw/stage.
>>
>
> Is this also what is occurring during the meta-intel builds?
>
Yes, and as you may have noticed it's been fixed and I pushed it to the 
RC3 branch and re-built the meta-intel builds.

>>> Please take a look or if you know of these issues, please let me know.
>>>
>>> Thanks
>>>
>>
>


      reply	other threads:[~2011-08-07 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 18:23 3 Failures in RC3 Saul Wold
2011-08-06 23:20 ` Saul Wold
2011-08-07 18:11   ` Flanagan, Elizabeth
2011-08-07 20:09     ` Saul Wold [this message]

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=4E3EF0E0.5000107@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Xiaofeng.Yan@windriver.com \
    --cc=elizabeth.flanagan@intel.com \
    --cc=richard.purdie@intel.com \
    --cc=yocto@yoctoproject.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.