From 66036553ac5439e48f8eeb0bcc2be3f42bb7850e Mon Sep 17 00:00:00 2001 From: Steve Langasek Date: Wed, 10 Jul 2019 14:30:28 -0700 Subject: [PATCH] Trigger linux rebuild test on upload of gcc-defaults The update of gcc to gcc-9 introduced a regression in buildability of anything relying on kernel headers. This could have been caught by the kernel's standard rebuild autopkgtest, but we currently only trigger the linux autopkgtest for source packages named gcc-N, which excludes gcc-defaults. Include gcc-defaults in the list of packages that trigger a linux rebuild test. Bug-Ubuntu: https://bugs.launchpad.net/bugs/1836100 --- britney2/policies/autopkgtest.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/britney2/policies/autopkgtest.py b/britney2/policies/autopkgtest.py index 556dda7..453850f 100644 --- a/britney2/policies/autopkgtest.py +++ b/britney2/policies/autopkgtest.py @@ -309,7 +309,7 @@ class AutopkgtestPolicy(BasePolicy): # serves no purpose. Just check some key packages which actually use # gcc during the test, and doxygen as an example for a libgcc user. if src.startswith('gcc-'): - if re.match(r'gcc-\d$', src): + if re.match(r'gcc-\d$', src) or src == 'gcc-defaults': # add gcc's own tests, if it has any srcinfo = self.britney.sources['unstable'][src] if 'autopkgtest' in srcinfo.testsuite: