[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2022-05-20 Thread Bug Watch Updater
** Changed in: gegl Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936901 Title: Tests of 0.4.30 crash on s390x To manage notifications about this bug go

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-09-10 Thread Bug Watch Updater
** Changed in: gegl (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936901 Title: Tests of 0.4.30 crash on s390x To manage notifications about

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-09-09 Thread Jeremy Bicha
This bug was fixed in the package gegl - 1:0.4.32-1 --- gegl (1:0.4.32-1) unstable; urgency=medium * Team upload * New upstream release * d/p/tests-Use-endiannness-dependent-reference-GEGL-buffers.patch, d/rules, d/clean: Avoid trying to load little-endian GEGL buffers

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-08-20 Thread Bug Watch Updater
** Changed in: gegl (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936901 Title: Tests of 0.4.30 crash on s390x To manage notifications about this bug go

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-07-20 Thread Bug Watch Updater
** Changed in: gegl (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936901 Title: Tests of 0.4.30 crash on s390x To manage notifications about this bug go

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-07-20 Thread Christian Ehrhardt 
Also reported to Debian since they are affected the same way https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991300 Depending on an upstream response we can then consider a) waiting for a fix as 0.4.30 is broken (real regression) and we don't want it to migrate b) it was always broken,

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-07-20 Thread Christian Ehrhardt 
** Bug watch added: gitlab.gnome.org/GNOME/gegl/-/issues #289 https://gitlab.gnome.org/GNOME/gegl/-/issues/289 ** Also affects: gegl via https://gitlab.gnome.org/GNOME/gegl/-/issues/289 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-07-20 Thread Christian Ehrhardt 
The very same on x86 shows a valid header: (gdb) p info->header.bytes_per_pixel $1 = 16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936901 Title: Tests of 0.4.30 crash on s390x To manage

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-07-20 Thread Christian Ehrhardt 
With that we see that the backtrace and values are: Thread 1 "gegl-imgcmp" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 49 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at

[Bug 1936901] Re: Tests of 0.4.30 crash on s390x

2021-07-20 Thread Christian Ehrhardt 
$ LC_ALL=C.UTF-8 MESON_TESTTHREADS=1 meson test rgb_params --print-errorlogs ninja: Entering directory `/root/gegl-0.4.30/obj-s390x-linux-gnu' ninja: no work to do. 1/1 gegl:composition / rgb_params FAIL 0.67s (exit status 250 or signal 122 SIGinvalid) The output from the failed tests: