[OE-core] Status of M3

[Zhenhua Luo]

Hi Richard, 

> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf
> Of Richard Purdie
> Sent: Thursday, March 03, 2016 10:23 PM
> To: openembedded-core <openembedded-core at lists.openembedded.org>
> Subject: [OE-core] Status of M3
> 
> I'm not sure people realise quite how much pain we've been suffering this
> week trying to get things stabilised for M3. To illustrate the kinds of problems,
> let me give an idea of the issues in the past few days. The resolved list:
> 
> * gobject-introspection has sstate relocation issues
> * gobject-introspection was missing a dependency
> * allarch contamination issues from gnomebase defaulting to g-i
> * gobject-introspection fails on x32
> * oe-selftest failures from the vm class changes
> * random createrepo issue
> * autobuilder workers were replaced with new distros
>   - one had firewall problems
>   - two had network interface problems
>   - another had VNC issues causing sanity test failures
> * there were autobuilder configuration changes
>   - eSDK changes failed initial
>   - increased ptest coverage failed initially
>   - uninative tarball publishing wasn't correct
>   - handle meta-poky transition
>   - handle adt-installer removal
> * uninative output name issues (BUILD_ARCH verses SDK_ARCH)
> * uninative sstate interaction issues (NATIVESDKSTRING)
> * ongoing pseudo retry issues
> * bitbake unpack improvements broke
> * canterall fonts broke oe-selftest
> * unsafe script references broke sanity tests
> * unsafe binary references broke in sanity tests due to prelink problem
> * meta-yocto -> meta-poky had multiple problems
> * race in do_rootfs_wicenv
> * eudev change broke oe-selftest
> * rpm upgrade went through multiple different build failures
> * toaster references to meta-yocto
> * I screwed up manually fixing a simple merge breaking builds. Twice :(
> 
> Things which still break:
> 
> * rpm upgrade causes smart remove to not function
> * gobject-introspection breaks on multilib with python-pygobject file
>   location issue
> * gobject-introspection fails on musl
> * createrepo has occasional failure with checksum mismatch
> * oe-selftest signing failure
> * sato application launch failures from glib issues due to prelink
> * meta-fsl-ppc breaks on eudev change (patch pending)
> * meta-fsl-ppc breakage blocks AB artefact publishing
[Luo Zhenhua-B19537] The eudev patch is merged, http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/commit/?id=2642cf5e8a6f8d11603acf016b8c075ebce00ec0, is there any other blocker issue? 


Best Regards,

Zhenhua

> There are only a small number of us who dive in and try and untangle the
> twisted web of which patch is causing which issue and try and put these things
> on a path to resolution
> 
> With this level of issues, we're simply not able to consider things like "why
> aren't you testing X?" or "can you test this patch to this component to get
> debugging?". There are 101 things that many of us would love to do but we
> need to improve the turnaround time of the tests we have. There are some
> simple things that come to mind that we could do:
> 
> a) optimisation of oe-selftest. Currently it takes around 8 hours but we could
> cut that time massively with some optimisation around the sstate cache and
> the way the tests are written. This one does catch many valid issues but its way
> too slow. Parallelism is also an option here.
> 
> b) switch to uninative by default to improve native/cross artefact reuse on the
> autobuilder. I have patches queued in -next to test this, see if we could switch
> to it.
> 
> c) switch to the new AB cluster when its ready (newer/faster hardware)
> 
> Volunteers for a) would be most welcome, other ideas welcome too.
> 
> Cheers,
> 
> Richard
> 
> 
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core