[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: base-installer: FTBFS?



Quoting Cyril Brulebois (kibi@debian.org):
> Christian PERRIER <bubulle@debian.org> (2014-10-13):
> > Just for the record, an attempt to build base-installer this morning
> > failed on my build machine.
> > 
> > I didn't send a bug report yet as I have a small doubt this could be
> > caused by a local problem. I'll try anyway to reproduce the build in
> > the upcomign days and will eventually file a BR in case the build
> > failure is reproducible.
> > 
> > (the failure happened during the "make test" phase: sorry no build logs
> > handy right now)
> 
> Builds fine on both wheezy and sid here. Maybe your pdebuild thing
> acting up again?

Dunno.

Here's the build failure:

   dh_auto_test
make[1]: Entering directory '/tmp/buildd/base-installer-1.151'
make -C kernel test
make[2]: Entering directory '/tmp/buildd/base-installer-1.151/kernel'
alpha: 24 passes, 0 failures.
amd64: 8 passes, 0 failures.
arm64: 24 passes, 0 failures.
armeb: 6 passes, 0 failures.
warning: Unknown armel subarchitecture 'ixp4xx'.
FAIL armel/slug.test arch_get_kernel_flavour 2.6 exit code
armel: 87 passes, 1 failures.
armhf: 78 passes, 0 failures.
hppa: 36 passes, 0 failures.
i386: 244 passes, 0 failures.
ia64: 22 passes, 0 failures.
m68k: 14 passes, 0 failures.
warning: Unknown mips subarchitecture 'qemu-mips32'.
FAIL mips/qemu.test arch_get_kernel_flavour 2.6 exit code
mips: 97 passes, 1 failures.
warning: Unknown mipsel subarchitecture 'qemu-mips32'.
FAIL mipsel/qemu.test arch_get_kernel_flavour 2.6 exit code
warning: Unknown mipsel subarchitecture 'r3k-kn02'.
FAIL mipsel/r3k-kn02.test arch_get_kernel_flavour 2.6 exit code
warning: Unknown mipsel subarchitecture 'r4k-kn04'.
FAIL mipsel/r4k-kn04.test arch_get_kernel_flavour 2.6 exit code
warning: Unknown mipsel subarchitecture 'cobalt'.
FAIL mipsel/r5k-cobalt.test arch_get_kernel_flavour 2.6 exit code
mipsel: 85 passes, 4 failures.
powerpc: 134 passes, 0 failures.
ppc64el: 16 passes, 0 failures.
s390x: 7 passes, 0 failures.
sh4: 20 passes, 0 failures.
sparc: 36 passes, 0 failures.
armel: 87 passes, 1 failures.
armhf: 78 passes, 0 failures.
hppa: 36 passes, 0 failures.
i386: 244 passes, 0 failures.
ia64: 22 passes, 0 failures.
m68k: 14 passes, 0 failures.
warning: Unknown mips subarchitecture 'qemu-mips32'.
FAIL mips/qemu.test arch_get_kernel_flavour 2.6 exit code
mips: 97 passes, 1 failures.
warning: Unknown mipsel subarchitecture 'qemu-mips32'.
FAIL mipsel/qemu.test arch_get_kernel_flavour 2.6 exit code
warning: Unknown mipsel subarchitecture 'r3k-kn02'.
FAIL mipsel/r3k-kn02.test arch_get_kernel_flavour 2.6 exit code
warning: Unknown mipsel subarchitecture 'r4k-kn04'.
FAIL mipsel/r4k-kn04.test arch_get_kernel_flavour 2.6 exit code
warning: Unknown mipsel subarchitecture 'cobalt'.
FAIL mipsel/r5k-cobalt.test arch_get_kernel_flavour 2.6 exit code
mipsel: 85 passes, 4 failures.
powerpc: 134 passes, 0 failures.
ppc64el: 16 passes, 0 failures.
s390x: 7 passes, 0 failures.
sh4: 20 passes, 0 failures.
sparc: 36 passes, 0 failures.
kfreebsd-amd64: 16 passes, 0 failures.
kfreebsd-i386: 32 passes, 0 failures.
Makefile:4: recipe for target 'test' failed
make[2]: *** [test] Error 1
make[2]: Leaving directory '/tmp/buildd/base-installer-1.151/kernel'
Makefile:32: recipe for target 'test' failed
make[1]: *** [test] Error 2

That happens when building with:
pdebuild --pbuilder cowbuilder -- --basepath /var/cache/pbuilder/base-sid.cow --distribution sid


The same happens when building with gbp (configured to build with
pbuilder as well).

Attachment: signature.asc
Description: Digital signature


Reply to: