On Mon, 2023-11-20 11:03:36 -0500, Christos Zoulas wrote:
> Since diffoscope is still timing out for he single file it finds inconsistent
> (
> https://tests.reproducible-builds.org/netbsd/netbsd.html)
> is there a way to download the files it compares so that We can do this
> manually? Perhaps p
Since diffoscope is still timing out for he single file it finds inconsistent
(https://tests.reproducible-builds.org/netbsd/netbsd.html)
is there a way to download the files it compares so that We can do this
manually? Perhaps print the URLs of the inputs when
it runs out of memory?
Thanks,
chr
On Thu, 2023-11-16 14:28:03 +, Holger Levsen wrote:
> On Thu, Nov 16, 2023 at 03:20:12PM +0100, Jan-Benedict Glaw wrote:
> > So... Stack dumps and crashing is quite okay. We don't expect our
> > parents or grandparents to use it, do we?
>
> I know at least one lawyer who uses diffoscope to
On Thu, 2023-11-16 14:13:14 +, Holger Levsen wrote:
> > However:
> [...]
> > > — https://docs.python.org/2/library/exceptions.html#exceptions.MemoryError
> > ... so this may not work in all situations.
>
> hmm. as a user I'd really like a mode where *no* tracebacks and other similar
> "scary
On Thu, Nov 16, 2023 at 03:20:12PM +0100, Jan-Benedict Glaw wrote:
> When a program cannot really continue its expected flow, I'm all for a
> stackdump and hard-crashing afterwards!
*g*
> So... Stack dumps and crashing is quite okay. We don't expect our
> parents or grandparents to use it, do w
On Thu, 2023-11-16 13:56:05 +, Chris Lamb
wrote:
> Holger Levsen wrote:
>
> > I think there is definitly an UI bug in diffoscope here. If/when diffoscope
> > runs out of memory, it should state that clearly and not throw 42 lines of
> > traceback at the user.
>
> Good idea. I've added that
On Thu, Nov 16, 2023 at 01:56:05PM +, Chris Lamb wrote:
> > I think there is definitly an UI bug in diffoscope here. If/when diffoscope
> > runs out of memory, it should state that clearly and not throw 42 lines of
> > traceback at the user.
> Good idea. I've added that here:
>
> https://sal
Holger Levsen wrote:
> I think there is definitly an UI bug in diffoscope here. If/when diffoscope
> runs out of memory, it should state that clearly and not throw 42 lines of
> traceback at the user.
Good idea. I've added that here:
https://salsa.debian.org/reproducible-builds/diffoscope/com
On Wed, Nov 15, 2023 at 02:30:05PM +, Chris Lamb wrote:
> Holger Levsen wrote:
> > https://jenkins.debian.net/job/reproducible_netbsd/1029/console
> > contains this, which IMO should not happen and is an issue in
> > diffoscope:
> >
> > Traceback (most recent call last):
> > File "/usr/lib/py
Holger Levsen wrote:
> https://jenkins.debian.net/job/reproducible_netbsd/1029/console
> contains this, which IMO should not happen and is an issue in
> diffoscope:
>
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 767,
> in main
> sys.e
On 2023-11-15 4:29 am, Holger Levsen wrote:
On Mon, Nov 06, 2023 at 10:42:05AM +, Chris Lamb wrote:
Christos Zoulas wrote:
> For weeks now there is no useful output from diffoscope. Is there anything I
> can do to help debug the issue?
>
> tests.reproducible-builds.org[eeB]
> Wed 1
On Mon, Nov 06, 2023 at 10:42:05AM +, Chris Lamb wrote:
> Christos Zoulas wrote:
>
> > For weeks now there is no useful output from diffoscope. Is there anything I
> > can do to help debug the issue?
> >
> > tests.reproducible-builds.org[eeB]
> > Wed 1 Nov 23:35:09 UTC 2023 - diffoscop
Jan-Benedict Glaw wrote:
> I cannot help with diffoscope. BUT I changed the NetBSD rb script to
> use two different build pathes which resulted in differences in
> comp.tar.gz.
Oh, good work tracking that down.
> REPROFLAGS+= -fdebug-prefix-map=\$$DESTDIR=
> +REPROFLAGS+= -fmacro-prefix-map=\$$
Christos Zoulas wrote:
> For weeks now there is no useful output from diffoscope. Is there anything I
> can do to help debug the issue?
>
> tests.reproducible-builds.org[eeB]
> Wed 1 Nov 23:35:09 UTC 2023 - diffoscope 251 produced no output for
> x86_64-amd64/amd64/binary/sets/comp.tar.xz
Hi!
On Sun, 2023-11-05 11:16:29 -0500, Christos Zoulas wrote:
> For weeks now there is no useful output from diffoscope. Is there anything I
> can do to help debug the issue?
>
> tests.reproducible-builds.org[eeB]
> Wed 1 Nov 23:35:09 UTC 2023 - diffoscope 251 produced no output for
> x
Hi,
For weeks now there is no useful output from diffoscope. Is there anything I
can do to help debug the issue?
Thanks,
christos
https://tests.reproducible-builds.org/netbsd/dbd/x86_64-amd64/amd64/binary/sets/comp.tar.xz.html
Wed 1 Nov 23:35:09 UTC 2023 - diffoscope 251 produced no output for
16 matches
Mail list logo
