Holger Levsen wrote:
> I'm not sure how --debug output should survive, but you mean just
> running diffoscope with an added --debug option?
Ah, yeah. It won't survive from Jenkins' log perspective, huh?
Hmm, the --debug output could perhaps to be directed straight to an
on-disk file. Given that
On Tue, May 14, 2024 at 11:43:29AM +0100, Chris Lamb wrote:
> Ah, I was hoping that the systemd slice apparatus would be able to
> contain any traceback, but now that I think of it, being OOM-killed is
> not quite the same as CPython-level crash (and thus traceback).
:)
> >
Holger Levsen wrote:
>> Hm, I can't seem to reproduce the crash with these files. In the first
>> instance, can you paste a traceback or similar of the crash in
>> question? Maybe it is fixable just from that without having to find
>> and upload more files, etc.
>
> I don't have a traceback as
On Wed, May 08, 2024 at 03:07:00PM +0100, Chris Lamb wrote:
> Hm, I can't seem to reproduce the crash with these files. In the first
> instance, can you paste a traceback or similar of the crash in
> question? Maybe it is fixable just from that without having to find
> and upload more files, etc.
Holger Levsen wrote:
> I'm attaching the crashing artifacts now to this bug report, however minus
> the orig.tar.gz files, though I suppose that the .deb files are enough to
> crash diffoscope anyway...
Hm, I can't seem to reproduce the crash with these files. In the first
instance, can you
Package: diffoscope
Version: 264
Severity: normal
X-Debbugs-Cc: team+pkg...@tracker.debian.org
Dear Maintainer,
diffoscope crashes when comparing the build results of src:dasel. To make it
more fun, src:dasel is only unreproducible on i386 (out of our four tested
archs, amd64/i386/arm64/armhf)
6 matches
Mail list logo
