All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky <poky@yoctoproject.org>
Subject: Re: Master stability update
Date: Tue, 25 Jan 2011 22:58:21 -0800	[thread overview]
Message-ID: <4D3FC60D.5000003@intel.com> (raw)
In-Reply-To: <1295993245.27814.133.camel@rex>

On 01/25/2011 02:07 PM, Richard Purdie wrote:
> We merged the features into master. I just want to highlight the status
> of the following issues:
>
> * pseudo problem causing failure of meta-toolchain and corruption of
> certain file permissions - fixed in master
>
> * the -live image issues some people and the autobuilder were seeing -
> fixed in master
>
> * the perf issue for linux-yocto-stable - fixed in master
>
> The following are know issues with master:
>
> * Using rm_work and switching machines to machines of the same
> "multimachine" architecture breaks.
>
> * When switching machines of the same "multimachine" architecture (e.g.
> emenlow to atom-pc), some sstate packages are changing checksums when at
> first glance they shouldn't (e.g. perl do_install). A quick scan of my
> sstate directory:
>
> $ ls *core2* | sed -e 's#core2-2-.*_#core2-2_#' | sort | uniq -cd | grep -v siginfo
>
> yields:
>
>        2 sstate-libzypp-core2-poky-linux-0.0-git0+4494797d5b0369365b1af63921de45b197ead64f-r6-core2-2_deploy-ipk.tgz
>        2 sstate-libzypp-core2-poky-linux-0.0-git0+4494797d5b0369365b1af63921de45b197ead64f-r6-core2-2_deploy-rpm.tgz
>        2 sstate-libzypp-core2-poky-linux-0.0-git0+4494797d5b0369365b1af63921de45b197ead64f-r6-core2-2_package.tgz
>        2 sstate-libzypp-core2-poky-linux-0.0-git0+4494797d5b0369365b1af63921de45b197ead64f-r6-core2-2_populate-sysroot.tgz
>        2 sstate-netbase-core2-poky-linux-4.44-r0-core2-2_deploy-ipk.tgz
>        2 sstate-netbase-core2-poky-linux-4.44-r0-core2-2_deploy-rpm.tgz
>        2 sstate-netbase-core2-poky-linux-4.44-r0-core2-2_package.tgz
>        2 sstate-netbase-core2-poky-linux-4.44-r0-core2-2_populate-sysroot.tgz
>        2 sstate-perl-core2-poky-linux-5.12.2-r0-core2-2_deploy-ipk.tgz
>        2 sstate-perl-core2-poky-linux-5.12.2-r0-core2-2_deploy-rpm.tgz
>        2 sstate-perl-core2-poky-linux-5.12.2-r0-core2-2_package.tgz
>        2 sstate-perl-core2-poky-linux-5.12.2-r0-core2-2_populate-sysroot.tgz
>        2 sstate-rpm-core2-poky-linux-5.1.10-r8-core2-2_deploy-ipk.tgz
>        2 sstate-rpm-core2-poky-linux-5.1.10-r8-core2-2_deploy-rpm.tgz
>        2 sstate-rpm-core2-poky-linux-5.1.10-r8-core2-2_package.tgz
>        2 sstate-rpm-core2-poky-linux-5.1.10-r8-core2-2_populate-sysroot.tgz
>        2 sstate-sat-solver-core2-poky-linux-0.0-git0+aa799f7bae0ec055e0e527203635001bb7346dbc-r2-core2-2_deploy-ipk.tgz
>        2 sstate-sat-solver-core2-poky-linux-0.0-git0+aa799f7bae0ec055e0e527203635001bb7346dbc-r2-core2-2_deploy-rpm.tgz
>        2 sstate-sat-solver-core2-poky-linux-0.0-git0+aa799f7bae0ec055e0e527203635001bb7346dbc-r2-core2-2_package.tgz
>        2 sstate-sat-solver-core2-poky-linux-0.0-git0+aa799f7bae0ec055e0e527203635001bb7346dbc-r2-core2-2_populate-sysroot.tgz
>        2 sstate-zypper-core2-poky-linux-1.4.7-git0+9eb0e248e06c8d20ad054be2439149d9ede37531-r3-core2-2_deploy-ipk.tgz
>        2 sstate-zypper-core2-poky-linux-1.4.7-git0+9eb0e248e06c8d20ad054be2439149d9ede37531-r3-core2-2_deploy-rpm.tgz
>        2 sstate-zypper-core2-poky-linux-1.4.7-git0+9eb0e248e06c8d20ad054be2439149d9ede37531-r3-core2-2_package.tgz
>        2 sstate-zypper-core2-poky-linux-1.4.7-git0+9eb0e248e06c8d20ad054be2439149d9ede37531-r3-core2-2_populate-sysroot.tgz
>
> which isn't too bad but shows there are some issues creeping in there.
> These need investigating and fixing, there is a strong rpm theme going
> on there. Also note this was just a minimal image, sato will likely
> reveal other issues.
>
> Cheers,
>
> Richard
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>

We are looking pretty good after the nightly has been running, a couple 
of issues were discovered by the Autobuilder, but we are more stable 
than we have been for a while.

Thanks to everyone for their hard work.

Seems that we have a couple of additional issues that need to be addressed.

1) Recent changes to the send-pull-request have caused the problem with 
the email now coming from poky-bounces.
    * dvhart or sgarman should investigate this please

2) atom-pc connman failure, Dongxiao may have already submitted a patch

3) emenlow rootfs failure, may be related to zypper/rpm, need to verify 
with Mark and his patch.

Thanks
     Sau!


  parent reply	other threads:[~2011-01-26  6:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 22:07 Master stability update Richard Purdie
2011-01-26  2:45 ` Xu, Dongxiao
2011-01-26  2:52   ` Tian, Kevin
2011-01-26  3:05     ` Tian, Kevin
2011-01-26  3:51       ` Mark Hatle
2011-01-26 11:42         ` Richard Purdie
2011-01-26  3:52       ` Xu, Dongxiao
2011-01-26  3:55         ` Xu, Dongxiao
2011-01-26 10:01         ` Richard Purdie
2011-01-26 10:31           ` Tian, Kevin
2011-01-26  6:58 ` Saul Wold [this message]
2011-01-26  7:01   ` Xu, Dongxiao
2011-01-27 12:45 ` Koen Kooi
2011-01-27 15:06   ` Richard Purdie
2011-01-27 15:35     ` Koen Kooi
2011-01-27 17:01       ` Koen Kooi
2011-01-27 21:45       ` Richard Purdie
2011-01-27 23:33         ` Koen Kooi
2011-01-28  7:56         ` Koen Kooi
2011-01-28 16:59           ` Richard Purdie
2011-01-28 17:42             ` Koen Kooi

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=4D3FC60D.5000003@intel.com \
    --to=saul.wold@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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.