On Thu, Nov 03, 2016 at 01:12:38PM +0100, Erich Schubert wrote: > severity 843038 wishlist > thanks > > Hi, > The test that failed is CPU sensitive. > Yes, it should probably be disabled, but does not any "serious" bug if it > fails on a heavily loaded machine. > > In particular, the solution obviously is to just not run the test at all. > That is not really an improvement either...
The reason I reported this as serious is release policy: https://release.debian.org/stretch/rc_policy.txt which says that packages must autobuild without failure. The common interpretation for this is that packages must *always* autobuild, not just "most of the time" and not just randomly. If you do not consider this to be RC, that's fine, but that's why the sarge-ignore tag exists. Thanks.
