From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Recent build issues.
Date: Mon, 03 Jan 2011 15:38:36 -0500 [thread overview]
Message-ID: <4D2233CC.7020707@windriver.com> (raw)
In-Reply-To: <DC74E0187B44084E9AD28300B75DFE300557D6E8@orsmsx504.amr.corp.intel.com>
On 10-12-23 05:08 PM, Flanagan, Elizabeth wrote:
> Recent build issues:
>
> - There seem to be a few issues going on with sanity testing:
>
> First, I've made a change to how sanity tests are run on the autobuilder that should speed them up some. bitbake @ -c qemuimagetest creates a rootfs. I've switched this to bitbake @ -c qemuimagetest_standalone, so this shouldn't create a rootfs and should use the one already existing. We should see some performance improvement with this. I thought this had been included in my pull with BB 0.8.3 but I must have not included it.
>
> Next, the following bugs have been making it difficult to track down build failures:
>
> Sanity Test Boot test returns invalid results.
> http://bugzilla.pokylinux.org/show_bug.cgi?id=611
>
> Sanity tests do not always kill QEMU once timeout is reached
> http://bugzilla.pokylinux.org/show_bug.cgi?id=595
>
> There are also sanity test failures in a few images:
>
> qemuarm poky-image-sato
> qemuarm poky-image-minimal
> qemumips poky-image-sato
>
> mips seems to have run poky-image-minimal ok, but with Bug #611, I can't be sure that is the case and I doubt it's actually the case. My inclination is that there is an issue with arm and mips builds that should be looked at.
>
> - PPC is broken.
>
> PPC is having serious issues that seem to revolve around linux-yocto-2.6.37. Bruce I believe is working on this. Can anyone give an update around where this stands?
Were we talking build or boot for this one ? The slow boot is only
being seen during auto-tests, and I've never reproduced it here.
I'm looking for someone who has time to debug this by tweaking
the kernel configuration, but as for what we produce for qemuppc
the configuration is sane and boots fine. Does anyone who can
reproduce this have time to look into it a bit more, or get me
access to a reproducing environment ?
Bruce
>
> I'm running nightly-incremental and nightly now to pull in some changes made this morning and to prepare for weekend delivery to QA. I'll send out those build results on Sunday (or whenever the build finishes.)
> -b
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2011-01-03 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 22:08 Recent build issues Flanagan, Elizabeth
2010-12-24 0:22 ` Richard Purdie
2010-12-24 0:53 ` Mark Hatle
2010-12-24 1:31 ` Xu, Jiajun
2011-01-03 20:38 ` Bruce Ashfield [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=4D2233CC.7020707@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=elizabeth.flanagan@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.