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.bzr-import-20160707
parent
97da2de23f
commit
30b6af1175
Loading…
Reference in new issue