These tests are maintained outside of the package anyway.
On the coming merge of a 2.3 version I'm going to propose to leave them just in git+ssh://git.launchpad.net/qa-regression-testing where they are maintained and used on SRU/Merge/CVE activity, but no more use them as autopkgtest.
That will avoid the issue described in this bug as these tests are semi-manual and whoever is working on SRU/Merge/CVE can sort out if these are really just flaky.
Note: I want to remove them for reoccurring issues due to the redundancy, not for this bug here - this is just a side effect.
These tests are maintained outside of the package anyway. //git.launchpad .net/qa- regression- testing where they are maintained and used on SRU/Merge/CVE activity, but no more use them as autopkgtest.
On the coming merge of a 2.3 version I'm going to propose to leave them just in git+ssh:
That will avoid the issue described in this bug as these tests are semi-manual and whoever is working on SRU/Merge/CVE can sort out if these are really just flaky.
Note: I want to remove them for reoccurring issues due to the redundancy, not for this bug here - this is just a side effect.