From: Saul Wold <sgw@linux.intel.com>
To: Saul Wold <sgw@linux.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: Sat, 06 Aug 2011 16:20:36 -0700 [thread overview]
Message-ID: <4E3DCC44.6050904@linux.intel.com> (raw)
In-Reply-To: <4E3D86A2.9080802@linux.intel.com>
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.
> 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.
> Please take a look or if you know of these issues, please let me know.
>
> Thanks
>
next prev parent reply other threads:[~2011-08-06 23:20 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 [this message]
2011-08-07 18:11 ` Flanagan, Elizabeth
2011-08-07 20:09 ` Saul Wold
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=4E3DCC44.6050904@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Xiaofeng.Yan@windriver.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.