Martin Pitt 21fec5d92a Only trigger autopkgtests for some key packages for gcc-* ...

Through the usual reverse dependency triggering, gcc-* usually triggers many
hundreds of (mostly universe) tests via libgccN. But:

 - This does not help to prevent compiler regressions: as all packages are
   built in -proposed anyway, the new compiler is being used immediately, so we
   can't hold it back in -proposed.

 - It does not trigger toolchain tests which actually are affected, most
   importantly binutils and linux.

 - This puts enormous stress onto our test infrastructure.

So special case gcc by triggering binutils and linux, and fglrx-installer as a
typical (and important) example of a DKMS package which also needs a compiler,
and libreoffice as our favourite tool chain stress test to cover libgccN.

2015-09-16 08:03:17 +02:00

..

__init__.py

Change autopkgtest tests to check YAML instead of HTML

2015-08-25 17:11:14 +02:00

mock_swift.py

tests/mock_swift.py: Fix ResourceWarning due to unclosed log file

2015-09-14 15:15:37 +02:00

test_autopkgtest.py

Only trigger autopkgtests for some key packages for gcc-*

2015-09-16 08:03:17 +02:00

test_boottest.py

make tests/test_* executable

2015-08-26 15:29:49 +02:00