> On Feb 17, 2020, at 13:54, Anatoly Pugachev <mator...@gmail.com> wrote: > > On Mon, Feb 17, 2020 at 11:12 PM Matthew Fernandez > <matthew.fernan...@gmail.com> wrote: >> >> Yikes, sorry. >> >> The test suite for this package auto-detects the number of CPUs and >> parallelises across all of them. This is not very well behaved when calling >> it from the outer build system, as it doesn’t pay attention to any -j flag >> you’ve passed there. To compound the situation, some of the individual test >> cases themselves are also multithreaded. >> >> I think the simplest solution is to force the test suite to always run >> single-threaded when called via ctest. Can I close this bug by making this >> change when packaging the next upstream release? Or do I also need to upload >> new packages for the existing versions in Debian? > > > Matthew, > > being "Version: 2020.01.27-1" is available in the repository , is it > possible to fix test suite to run single-threaded (or maybe -j2) via > debian package patch and bump version to "2020.01.27-2" and upload? > > Thanks.
Yes, good point, fair enough. I was midway through cutting a new upstream release when the first report arrived, so I’ll make the fix there and package that, and then backport it to a 2020.01.27-2 upload. The new test suite responsible for this hammering was actually added several upstream releases back, but it looks like 2020.01.27-1 is the only package to make it through to unstable so far, so I assume I don’t need to backport this change to -2 uploads for older packages that only ever existed in testing.
