Martin Pitt 30b6af1175 Autopkgtest: Don't track "ever passed" for kernel triggers ...

We trigger independent tests for every linux/linux-meta* reverse dependencies,
as they run under the triggering kernel. Thus "ever passed" is rather
meaningless for these as we don't want to track this on a per-trigger basis (as
it would be wrong for everything else but kernels). This led to a lot of false
regressions, as some DKMS modules only work on some kernel flavours.

The kernel team is doing per-kernel regression analysis of the test results, so
we don't need to duplicate this logic in britney. Thus effectively disable the
"Regression" state for kernel reverse dependencies, and rely on the kernel
test machinery to untag the tracking bug only if there are no actual
regressions.

2015-09-29 21:42:05 +02:00

..

__init__.py

Autopkgtest tests: Publish test packages on all architectures by default

2015-09-16 16:49:14 +02:00

mock_swift.py

tests/mock_swift.py: Support adding testinfo.json

2015-09-17 11:05:33 +02:00

test_autopkgtest.py

Autopkgtest: Don't track "ever passed" for kernel triggers

2015-09-29 21:42:05 +02:00

test_boottest.py

make tests/test_* executable

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