You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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.		10 years ago
..
__init__.py	Change autopkgtest tests to check YAML instead of HTML	10 years ago
mock_swift.py	tests/mock_swift.py: Fix ResourceWarning due to unclosed log file	10 years ago
test_autopkgtest.py	Only trigger autopkgtests for some key packages for gcc-*	10 years ago
test_boottest.py	make tests/test_* executable	10 years ago