Bug#804406: autopkgtest: add a restriction or a feature to permit tests of different expected duration

Jerome Benoit calculus at rezozer.net
Sun Nov 8 07:49:23 UTC 2015


Package: autopkgtest
Version: 3.17.2~bpo8+1
Severity: wishlist

Dear Maintainer Team:

	It appears that one of my current tests (make-longcheck for
	the gmp-ecm pacakge, not to mention it) constantly caught a TERM
	signal after a fix duration of abour 2h50. For some tests, this
	duration limit is certainly very long; but for some other tests
	the time scale can far longuer. It would be nice to have a mean
	to specify qualitatively the expected time scale of the involved
	test (e.g., short, long, very_long, extremely_long, etc).

hth,
Jerome


-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages autopkgtest depends on:
ii  apt-utils       1.0.9.8.1
ii  libdpkg-perl    1.17.25
ii  procps          2:3.3.9-9
ii  python3         3.4.2-2
ii  python3-debian  0.1.27

Versions of packages autopkgtest recommends:
pn  autodep8  <none>

Versions of packages autopkgtest suggests:
pn  lxc          <none>
pn  qemu-system  <none>
pn  qemu-utils   <none>
pn  schroot      <none>

-- no debconf information



More information about the autopkgtest-devel mailing list