[maemo-developers] More autobuilder problems (armel only)

[From: Andrew Flegg]

On Mon, Jun 30, 2008 at 12:14 PM, Ed Bartosh <eduard.bartosh at nokia.com> wrote:
> On Sun, 2008-06-29 at 15:57 +0100, ext Andrew Flegg wrote:
>>
>> I'm /fairly/ certain it's not related: an earlier build also failed,
>> without generating a 28MB summary.
>>
> Can you point me out to the initial sources, please?
> I'll look what's the issue there.

https://garage.maemo.org/builder/diablo/vim_7.0/sources/

My attempt to re-upload the package to get a smaller log resulted in
the following output by the builder (and nothing else):

summary.log:
    [2008-06-29 19:55:07] Processing package vim 7.0. Uploader: jaffa,
builder: builder1
    [2008-06-29 19:55:07] Building vim 7.0 for target
'maemo-diablo-armel-extras-devel'
    [2008-06-29 19:55:22] FAILED

armel.root.log.FAILED.txt:
[2008-06-29 19:47:32] ensuring dir
/scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/state
[2008-06-29 19:47:32] Cleaning Root
[2008-06-29 19:47:32] ensuring dir
/scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel
[2008-06-29 19:47:32] ensuring dir
/scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/work
[2008-06-29 19:47:32] ensuring dir
/scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/state
[2008-06-29 19:47:32] ensuring dir
/scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/result
[2008-06-29 19:47:32] ensuring dir
/scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel
[2008-06-29 19:47:35] Cleaning up...
[2008-06-29 19:47:37] Removing temporary target...
[2008-06-29 19:47:37] Done.

> My first guess is build failed because you didn't put everything which
> is needed to build vim into build-depends.

That might be it, but if so the error's very confusing: the configure
script didn't die complaining about unmet dependencies, it died - at
some point in the build - complaining about being unable to run
compiled C programs.

> The fact that it builds in your local environment simply means that you have all
> real build dependencies installed there.

At the moment, I've got a fairly clean install of 4.1. However, is it
possible to get a list of all the packages the auto-builder has
installed in its environment (preferably kept updated at a fixed URL)
so that it'd be possible for me (and maybe, at some point,
mud-builder) to run dpkg --set-selections to help ensure accuracy of
Build-Depends etc. before upload?

Making sure we've got tooling (and an evolved mud seems the most
sensible to me) to help developers streamline their autobuild
experience seems key to ensure they don't get pushed into
proliferating repos by creating their own because it's "easier".

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:andrew at bleb.org | http://www.bleb.org/