Re: [Gumstix-users] Proposed Solution for poor bitbake Quality Control?

[Steve S. <sa...@gm...>]

On Mon, Aug 23, 2010 at 7:33 AM, Eric Wenger <eri...@gm...> wrote:
> Thanks Steve -- that should be helpful to users!  I was looking at the top
> of the list rather than the bottom (latest builds).

I should also note for the record that my build script for the
pre-built images uncomments the libgles packages in the image recipes
so that the SGX 3D support is enabled.

Steve


>
> --Eric
>
>
>
> On Mon, Aug 23, 2010 at 10:09 AM, Steve Sakoman <sa...@gm...> wrote:
>>
>> On Mon, Aug 23, 2010 at 6:25 AM, Eric Wenger <eri...@gm...>
>> wrote:
>> > Steve,
>> >
>> > I suggested on an earlier thread that you could post the git commit
>> > hashes
>> > with the factory/posted builds so that people could use those as
>> > baselines.
>> > Is there any possibility of getting that done?
>>
>> That information is already available.  For example look at the last
>> pre-built image:
>>
>> http://www.sakoman.com/feeds/omap3/glibc/images/overo/201008132038/
>>
>> You will note that there is a file with this information
>> (overo-oe-commit-id.txt):
>>
>>
>> http://www.sakoman.com/feeds/omap3/glibc/images/overo/201008132038/overo-oe-commit-id.txt
>>
>> There is also a file with md5sums for each of the images (md5sum.txt):
>>
>>
>> http://www.sakoman.com/feeds/omap3/glibc/images/overo/201008132038/md5sum.txt
>>
>> Steve
>>
>> > That would probably help a
>> > number of people to at least find a stable commit when needed.
>> >
>> > --Eric
>> >
>> > On Tue, Aug 17, 2010 at 1:08 PM, Steve Sakoman <sa...@gm...>
>> > wrote:
>> >>
>> >> On Tue, Aug 17, 2010 at 8:51 AM, AJ ONeal <coo...@gm...>
>> >> wrote:
>> >>
>> >> > How about something like this:
>> >> > All updates are done in the "moving-target" (unstable) branch
>> >>
>> >> That is the org.openembedded.dev branch.
>> >>
>> >> > Any time the "moving-target" branch will build a clean
>> >> > omap3-desktop-image
>> >> > without errors it is merged with the "just-works" (stable) branch
>> >>
>> >> That is the overo branch.  I merge with the upstream
>> >> org.openembedded.dev branch approximately once a week. (this info is
>> >> on the gumstix.net site IIRC)
>> >>
>> >> I then do builds of all of the "omap3" images and the
>> >> sakoman-gnome-image on my dev machine (Ubuntu 10.04 quad core).  I fix
>> >> anything that might be broken and then do automated builds of the same
>> >> images for both Beagle and Overeo on the www.sakoman.com machine
>> >> (Ubuntu 9.04 64 bit server dual core).  If successful then the result
>> >> is pushed to overo branch.
>> >>
>> >> In theory that should yield a "just works" branch.
>> >>
>> >> In practice people still have problems.  OE is a *very* complex build
>> >> environment that still has dependencies on the package set installed
>> >> on the build machine as well as lingering dependency issues that show
>> >> up randomly depending on the number of cores on your machine and your
>> >> settings for PARALLEL_MAKE and BB_NUMBER_THREADS.  That is why -c
>> >> clean and rebuilds of failing packages more often than not result in a
>> >> good build the second time around.
>> >>
>> >> If you find fixes for the above, by all means submit the patches to
>> >> the OE mailing list!  You will have many grateful users :-)
>> >>
>> >> > The "just works" branch.
>> >> > Then try to do a "bitbake world" on the "just-works" branches and tag
>> >> > that
>> >> > branch as special (or merge it with a "no-really-it-does-work"
>> >> > branch).
>> >>
>> >> Again, nice in theory.  But I have *never* seen a 'bitbake world'
>> >> succeed in real life :-)
>> >>
>> >> > Who is in charge anyway? Is that person interested in making things
>> >> > more
>> >> > reliable? Does that person want help?
>> >>
>> >> I guess I am the one currently "in charge" of the Overo branch.  Of
>> >> course I would like things to be more reliable!  But this is a very
>> >> big effort on a moving target, so the more folks that help the better.
>> >>  I'm one part-time consultant who is also doing board support for
>> >> u-boot and the linux kernel so there is only so much that I can
>> >> accomplish by myself.
>> >>
>> >> Again if you find fixes to OE issues, submitting them to the OE
>> >> mailing list is the right thing to do.  The Overo branch is 99.9%
>> >> identical to org.openembedded.dev -- we use a custom linux and u-boot
>> >> recipe so that we don't break every time someone upstream changes the
>> >> "one size fits all" recipes upstream.  We also have custom image
>> >> recipes to control what goes in the NAND.  If you find issues with
>> >> those recipes, the gumstix list is the place to post your patches.
>> >> But in my experience, the vast majority of build issues that people
>> >> encounter are generic OE issues.  Fixes for those should go to the OE
>> >> list (and a cc to the gumstix list would be nice).
>> >>
>> >> Steve
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> This SF.net email is sponsored by
>> >>
>> >> Make an app they can't live without
>> >> Enter the BlackBerry Developer Challenge
>> >> http://p.sf.net/sfu/RIM-dev2dev
>> >> _______________________________________________
>> >> gumstix-users mailing list
>> >> gum...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by
>> >
>> > Make an app they can't live without
>> > Enter the BlackBerry Developer Challenge
>> > http://p.sf.net/sfu/RIM-dev2dev
>> > _______________________________________________
>> > gumstix-users mailing list
>> > gum...@li...
>> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gum...@li...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>