Bug#991059: diffoscope: out-of-memory

2021-08-17 Thread Chris Lamb
Hi Roland, > If possible, I would like to see something like: > * If the return value of unsquashfs is non-zero, look whether stderr > only contains lines like > 'create_inode: could not create character device ./dev/console, because > you're not superuser!' > * If that is the case, resume

Bug#991059: diffoscope: out-of-memory

2021-08-16 Thread Holger Levsen
On Sat, Aug 14, 2021 at 04:01:34PM +0200, Roland Clobus wrote: > > (A side question: can you confirm whether diffoscope is running as > > root or not in your particular Jenkins test? I don't want to > > misinterpret the logs.) > I'm 99.9% sure that I'm not running as root, because I would have

Bug#991059: diffoscope: out-of-memory

2021-08-13 Thread Chris Lamb
Hi Roland, > > So it appears to me that different code is activated for regular users > > and root. In addition to the filesystem device difference (discussed below), the other highly relevant difference is that processes run as root are terminated by the OOM killer with a slower priority. This

Bug#991059: diffoscope: out-of-memory

2021-08-12 Thread Roland Clobus
Answering my own mail. On 11/08/2021 11:49, Roland Clobus wrote: > So it appears to me that different code is activated for regular users > and root. I think I've found the cause for the different code paths. The squashfs image contains devices, which can only be extracted as root. Output of

Bug#991059: diffoscope: out-of-memory

2021-08-11 Thread Roland Clobus
On 15/07/2021 18:41, Mattia Rizzolo wrote: > On Wed, Jul 14, 2021 at 08:31:48PM +0200, Roland Clobus wrote: >> The difference between these two files is located inside a squashfs >> file, which is inside the iso file. >> During the invocation of diffoscope, diffoscope needs lots of memory >>