how to detect unstable builds

how to detect unstable builds

[Andreas Schultz]

Hi,

Unstable might be not the right term, but I couldn't think of another.

The issue is that two builds on exactly the same build host, produce
packages that have different runtime dependencies and also different
behaviors.

I encountered this problem with readline, but other package might have
it as well.

I try to build an image that contains systemd and (an modified) bind. The
declared dependencies of systemd contain readline, those of my version of
bind do not. With multiple parallel task, build order is not guaranteed
and bind might be build before or after readline.

bind's autoconf does check for readline and will link bind to it if
it finds it.

The outcome is that some builds contain a bind linked against readline,
while other contain a bind that is not linked against readline.

** QA hell breaks loose **

Is there a way to detect and/or prevent situations like this?

Regards
Andreas
-- 
-- 
Dipl. Inform.
Andreas Schultz

Re: how to detect unstable builds

[Richard Purdie]

On Wed, 2014-07-30 at 14:10 +0000, Andreas Schultz wrote:
> Hi,
> 
> Unstable might be not the right term, but I couldn't think of another.
> 
> The issue is that two builds on exactly the same build host, produce
> packages that have different runtime dependencies and also different
> behaviors.
> 
> I encountered this problem with readline, but other package might have
> it as well.
> 
> I try to build an image that contains systemd and (an modified) bind. The
> declared dependencies of systemd contain readline, those of my version of
> bind do not. With multiple parallel task, build order is not guaranteed
> and bind might be build before or after readline.
> 
> bind's autoconf does check for readline and will link bind to it if
> it finds it.
> 
> The outcome is that some builds contain a bind linked against readline,
> while other contain a bind that is not linked against readline.
> 
> ** QA hell breaks loose **
> 
> Is there a way to detect and/or prevent situations like this?

If linkage to a library that is not in DEPENDS happens, there is new
code which should detect this:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a202f8a66383787c899246c5fa14c862e5d7647d

Its not perfect but it should be better than we've ever had before and
is a start...

Cheers,

Richard

Re: how to detect unstable builds

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

On Wed, Jul 30, 2014 at 02:10:28PM +0000, Andreas Schultz wrote:
> Hi,
> 
> Unstable might be not the right term, but I couldn't think of another.
> 
> The issue is that two builds on exactly the same build host, produce
> packages that have different runtime dependencies and also different
> behaviors.
> 
> I encountered this problem with readline, but other package might have
> it as well.
> 
> I try to build an image that contains systemd and (an modified) bind. The
> declared dependencies of systemd contain readline, those of my version of
> bind do not. With multiple parallel task, build order is not guaranteed
> and bind might be build before or after readline.
> 
> bind's autoconf does check for readline and will link bind to it if
> it finds it.
> 
> The outcome is that some builds contain a bind linked against readline,
> while other contain a bind that is not linked against readline.
> 
> ** QA hell breaks loose **
> 
> Is there a way to detect and/or prevent situations like this?

see test-dependencies.sh script in oe-core or reports from it on oe-core
ML, latest is
http://lists.openembedded.org/pipermail/openembedded-core/2014-July/094924.html

buildhistory is also great to compare builds, but e.g.
files-in-image.txt report has a lot of noise from slightly different
binaries, see
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5866

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]