From: Tom Zanussi <tom.zanussi@intel.com>
To: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Status of release candidate: bernard-1.0rc1
Date: Mon, 28 Feb 2011 01:51:39 -0600 [thread overview]
Message-ID: <1298879499.2429.15.camel@elmorro> (raw)
In-Reply-To: <4D6B0F2C.9080401@intel.com>
On Sun, 2011-02-27 at 18:57 -0800, Elizabeth Flanagan wrote:
> Summary
> =======
>
> This weekend, we generated a release candidate for bernard based on the bernard branch
> of master at commit:
> e08dc5aaaeba61e332caab4a3df5750df6b49ac1
>
> and for BSPs based on the bernard branch of meta-intel at commit:
> 16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6
>
> Issues seen:
> ===========
>
> Build Infrastructure issues:
> ----------------------------
>
> - We had an issue with builder02 running out of disk space, so some of the build
> copying was done post-build. This did not effect the build and was dealt with
> manually after cleaning up the partition.
>
> - There is an issue with how package-index is being run. I will need to sync up
> with Jessica to verify how this should be incorporated into the build.
>
> - The sanity tests on builder02 failed because builder02 was unable to resolve
> "localhost". This has been corrected and the sanity tests re-run incrementally:
> http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3
>
> - The tarball generation buildstep is not branch aware. This will be fixed this week.
> In the meantime it was run manually.
>
>
> Sanity Test Issues:
> ----------------------------
>
> - zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato
>
>
> Build Issues:
> ----------------------------
>
> - BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
> - Failing to do_kernel_checkout
There are a couple problems with the jasperforest BSP. First, the
SRCREVs need updating, which I just submitted a patch for.
Even after that, though, there seems to be a problem with the kernel
repo the fetcher is getting. Even after clearing it out of git2, the
kernel repo that gets fetched into git2 and the build doesn't have the
jasperforest branch. A manual local clone of linux-yocto-2.6.37 does
contain the branch, though, and pointing the build to the local clone
finds the branch and builds(*) ok.
(*) until it gets to compiling perf - at that point it fails since the
branch doesn't yet have the perf compile fix moved from master.
Tom
> - Unpack issues around svn://svn.o-hand.com/repos
>
> - Beagleboard failed doing runstrip on uboot during do_populate_sysroot
>
>
> Build statistic:
> ----------------------------
>
> Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:
>
> real 109m52.400s
> user 393m58.840s
> sys 59m25.380s
>
> Build statistics for nightly-external are available at:
>
> http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/
>
> Open Defects:
> ----------------------------
>
> As of right now we have:
> 76 total open defects targeted for 1.0
>
> Critical: 0
> High: 14
> Medium: 53
> Low: 7
> Undetermined: 2
>
>
> Thanks for all those who helped with this weekends RC generation, especially sgw and RP__
>
> ------------------
> Elizabeth Flanagan
> Yocto Project
> Release Engineer
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-02-28 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 2:57 Status of release candidate: bernard-1.0rc1 Elizabeth Flanagan
2011-02-28 3:14 ` Lu, Lianhao
2011-02-28 7:51 ` Tom Zanussi [this message]
2011-02-28 16:40 ` Tom Zanussi
2011-03-01 7:37 ` Tom Zanussi
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=1298879499.2429.15.camel@elmorro \
--to=tom.zanussi@intel.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.