Bug#951497:

2020-03-15 Thread Matthew Fernandez
Just an update on some things relevant to this bug: * a new version of Rumur I uploaded, v2020.03.12-1, was just approved by Adam * Rumur v2020.01.27-2, my attempted final resolution to this bug, was removed from mentors due to the more recent upload For anyone following this bug at home or try

Bug#951497: I can't reproduce

2020-02-24 Thread Matthew Fernandez
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 An

Bug#951497: I can't reproduce

2020-02-24 Thread Adam Borowski
Hmm... it was me who reviewed+uploaded the current version, and it doesn't even put a strain on my box, despite using 4× as many cores but only 64GB memory. Ie, half the memory per thread. It also has an interesting pattern of CPU use: there's never any substantial load on any single thread, and

Bug#951497: rumur: building from sources makes machine un-usable or OOM/kills kernel

2020-02-17 Thread Matthew Fernandez
> On Feb 17, 2020, at 13:54, Anatoly Pugachev wrote: > > On Mon, Feb 17, 2020 at 11:12 PM Matthew Fernandez > 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

Bug#951497: rumur: building from sources makes machine un-usable or OOM/kills kernel

2020-02-17 Thread Anatoly Pugachev
On Mon, Feb 17, 2020 at 11:12 PM Matthew Fernandez 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 -

Bug#951497: rumur: building from sources makes machine un-usable or OOM/kills kernel

2020-02-17 Thread Matthew Fernandez
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 in

Bug#951497: rumur: building from sources makes machine un-usable or OOM/kills kernel

2020-02-17 Thread Anatoly Pugachev
Package: rumur Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? building rumur from sources on a debian sid (unstable): * What exactly did you do (or not do) that was effective (or ine