Source: mdanalysis Followup-For: Bug #1108309 X-Debbugs-Cc: 1108...@bugs.debian.org Control: tags -1 ftbfs
Santiago Vila wrote: > But the build logs from buildd.debian.org which I quoted in my initial > report, where the build fails with timeout: > ... > happened on machines with more than 2 CPUs, so by skipping the tests > if the number of CPUs is <= 2, we are certainly avoiding the problem > in some scenarios where we know the tests are quite useless, but not > in the buildds. > > So, to summarize, I don't think it was a good suggestion, and I'm sorry > that I realized now. Ok, thanks for clarifying, Santiago. In that case it's better for trixie to just skip all tests. That's gotten done now with a debci ban, but that doesn't let us test any movement from upstream (the ban prevents testing new code in experimental). So I'll upload -12 switching off tests for trixie. Drew
