From 632f542e632de0d592ed26e306da2846afc62384 Mon Sep 17 00:00:00 2001 From: Martin Pitt Date: Wed, 30 Sep 2015 17:45:12 +0200 Subject: [PATCH] Autopkgtest: Don't track "ever passed" for kernel triggers, part 2 In addition to not reading ever_passed for kernel triggers, we must also not write it for those. Otherwise we introduce false regressions for e. g. "dkms" when some DKMS package always failed on the main kernel but succeeds on one flavour. --- autopkgtest.py | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/autopkgtest.py b/autopkgtest.py index f0b50d7..9a6c38c 100644 --- a/autopkgtest.py +++ b/autopkgtest.py @@ -466,8 +466,13 @@ class AutoPackageTest(object): # add this result src_arch_results = self.test_results.setdefault(src, {}).setdefault(arch, [stamp, {}, False]) if passed: - # update ever_passed field - src_arch_results[2] = True + # update ever_passed field, unless we got triggered from + # linux-meta*: we trigger separate per-kernel tests for reverse + # test dependencies, and we don't want to track per-trigger + # ever_passed. This would be wrong for everything except the + # kernel, and the kernel team tracks per-kernel regressions already + if not result_triggers or not result_triggers[0][0].startswith('linux-meta'): + src_arch_results[2] = True if satisfied_triggers: for trig in satisfied_triggers: src_arch_results[1].setdefault(ver, {})[trig[0] + '/' + trig[1]] = passed