[poky] Master stability update

[Xu, Dongxiao]

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. 

After sysroot is per machine, we may need to reserve the "image" folder even when rm_work, since for the second machine build, do_populate_sysroot and do_package will be re-run to populate files into a different sysroot folder. 

> 
> * 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:  

I also have a look at my local build sstate directories, there are 17 packages whose prebuilt result could not shared betweeen atom-pc and emenlow. Some of them may be not a problem since there are ${MACHINE} variables used in do_install(), some others are strange why do_install will have two different signatures between two different machines. 

I will spend some time investigating it.

Thanks,
Dongxiao

> 
> $ 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky