Source: mdanalysis Followup-For: Bug #1108309 Upstream has no* special requirements for their bug reports, so please do file with them directly at https://github.com/MDAnalysis/mdanalysis/issues
It's actually a good idea to do that, because they'll be able to discuss directly what their intentions are for multiprocessor testing, compared to the conditions that you (and debci) are using in our testing. They are proud of their code and they want their tests to pass reliably, so it can be a constructive dialogue with them. * the only catch is that they release regularly, so our debian version is a little behind the latest upstream release. There may be improvements they've already made they we haven't caught yet. But the problems with their tests are longstanding, so I think it's still worth filing the issue with them. In regards to the severity of this bug, the faiing tests will no longer block migration to testing after marking them with Restriction: flakey. So in that regard this issue is Severity: important not Severity: serious, unless you prefer to mean severity "serious" in the sense that trixie shouldn't be providing the package even with tests marked flakey.
