You’re definitely testing v2020.01.27-1 right, Adam? I would think you probably are, but I ask because the version you uploaded for me last week (v2020.02.17-1) is not the problem one. v2020.02.17-1 should not reproduce this issue as I also made the fix there before uploading it. The problems Anatoly encountered were with v2020.01.27-1.
This is the first time I’ve had to make an updated release for a non-current version of a package, so it’s possible I did something unorthodox or confusing in my v2020.02.17-2 upload as well. FWIW the situation Anatoly identified is a genuine problem for both the Debian package and the upstream native repo. The build system didn’t pass the test suite any parallelism constraints and the test suite tries to monopolise all cores in this scenario. Note that even after the fix you may see brief periods of multicore load because some of the test cases themselves do parallel work.
