Results for mass autopkgtest run for all perl packages [2014-09-11]
On Fri, Sep 12, 2014 at 07:05:31AM +0200, Martin Pitt wrote:
> Yesterday I started another run with the complete batch and let it run
> over night. To avoid the problem of having to kill hanging tests (most
> often just in their cleanup, the actual tests usually work fine) I ran
> them with --timeout-test=300 (i. e. 5 minutes). This killed 14 tests
> (grep for "testbed failed: timed out").
I could only find seven of them with that grep? I went through them:
These three are due to #761596 (autopkgtest: overrides default SIGINT handler).
Busy loop looking reading a non-existent file. Fixed in git, pending upload.
Lengthy author test that isn't run normally (and needs network access),
caused by us recursing into subdirectories under 't/'. Neither of the
normal Perl build systems (ExtUtils::MakeMaker and Module::Build) do that,
so we shouldn't either. Will be fixed in pkg-perl-tools 0.15.
Busy loop missing user interaction due to us not setting the
AUTOMATED_TESTING environment variable. That one and NONINTERACTIVE_TESTING
will be exported in pkg-perl-tools 0.15.
Genuinely lengthy tests (703963 of them!), took over seven minutes on
the amd64 buildd.
I've also made the smoke test execute test.pl in addition to t/*.t. The
implicit test generation logic in autopkgtest should do the same, at least
once pkg-perl-tools 0.15 is uploaded. This potentially affects 168 packages
that had their tests skipped until now.
Niko Tyni ntyni at debian.org