On Thu, 21 Jul 2016 11:19:46 +0200, Chris Lamb wrote: > > - by disabling them, even if they fail gracefully, in order to follow > > policy, we effectively castrate the tests, which doesn't seem right > > from a QA POV. > Mm, agreed. Moving these tests to the autopkgtest infrastructure is one > fix but it's not "that" clean a solution..
Well, right, autopkgtest is the next question. If a test is forbidden to leak to external parties the fact that it's being run during build, the same is probably true by analogy for autopkgtests? (Recently I disabled the same tests for both build + autopkgtests.) Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #211: Lightning strikes.
