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
2011-12-23 11:16:32 +01:00
2008-05-20 17:37:56 +02:00
2015-08-24 20:46:42 +02:00
2015-08-26 16:25:25 +02:00
2015-07-01 15:49:06 +02:00
2015-04-26 18:20:11 +02:00
2015-04-26 18:20:10 +02:00
2011-07-06 18:31:45 +00:00

README for britney v2.0
=======================

Please write here some useful stuff.

Description
britney2-ubuntu fork which runs on ci.lubuntu.me
Readme GPL-2.0 9.4 MiB
Languages
Python 99.6%
Shell 0.3%