Bug#807617: FTBFS due to test-suite failures

[Guus Sliepen]

On Thu, Dec 10, 2015 at 11:41:06PM +0100, Michael Biebl wrote:

> Since version 0.8, the test-suite basically fails on all architectures
> as can be seen at
> https://buildd.debian.org/status/package.php?p=ifupdown=unstable
> 
> I can reproduce the problem on amd64 with a pbuilder build.
> >From a cursory glance it looks like the test suite needs files from the
> installed package (i.e. it looks for /lib/ifupdown/settle-dad.sh).
> 
> Shouldn't it use ./settle-dad.sh instead when running the test-suite?

It actually doesn't call settle-dad.sh at all. The problem is that the
testsuite is running ifup with the --no-act option, and compares the
output of it to the expected output as written in
debian/testbuild-linux. Ifup only calls /lib/ifupdown/settle-dad.sh if
it exists and is executable, but that of course depends on the build
environment. The expected output was written with the assumption that
/lib/ifupdown/settle-dad.sh is already there. So I'll have to fix that.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#807617: FTBFS due to test-suite failures

[Michael Biebl]

Source: ifupdown
Version: 0.8.2
Severity: serious

Since version 0.8, the test-suite basically fails on all architectures
as can be seen at
https://buildd.debian.org/status/package.php?p=ifupdown=unstable

I can reproduce the problem on amd64 with a pbuilder build.
>From a cursory glance it looks like the test suite needs files from the
installed package (i.e. it looks for /lib/ifupdown/settle-dad.sh).

Shouldn't it use ./settle-dad.sh instead when running the test-suite?


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information