Martin Pitt 2ebfc0bb8f Stop accepting results without recorded trigger
In situations where we don't have an up to date existing results.cache, the
fallback for handling test results would attribute old test results to new
requests, as we don't have a solid way to map them. This is detrimental for ad
hoc britney instances, like for testing PPAs, and also when we need to rebuild
our cache.

Ignore test results without a package trigger, and drop the code for handling
those.

The main risk here is that if we need to rebuild the cache from scratch we
might miss historic "PASS" results which haven't run since we switched to
recording triggers two months ago. But in these two months most of the
interesting packages have run, in particular for the development series and for
stable kernels, and non-kernel SRUs are not auto-promoted anyway.
2015-11-27 16:36:28 +01: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-09-25 11:25:21 -05: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
2015-11-27 08:16:55 +01: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%