Your message dated Thu, 17 Dec 2015 11:33:51 +0100 with message-id <[email protected]> and subject line Re: Bug#804406: autopkgtest: add a restriction or a feature to permit tests of different expected duration has caused the Debian Bug report #804406, regarding autopkgtest: add a restriction or a feature to permit tests of different expected duration to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 804406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804406 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Control: tag -1 wontfix Hello Jerome, Jerome Benoit [2015-11-08 8:49 +0100]: > 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. Right, that's the default --timeout-test=10000 (seconds). You should run your test with a longer timeout then. > 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). Sorry, this is too fuzzy to define exact semantics for those. The runtime of tests heavily depends on where you run them (architecture, old vs. new hardware, lots vs. little RAM, etc.), and tests should in general not make assumptions about the testbed they are running on, in order to stay as generic as possible. This kind of "list of tests which take a long time" is much better maintained in the layer above autopkgtest, i. e. the CI system. For example, I have two list "big packages" and "long tests" in https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/tree/worker-config-production/worker.conf So I'm closing this for autopkgtest. This rather sounds like an appropriate feature request for debci (if your test times out on ci.debian.net). Thanks! Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
