Your message dated Wed, 13 Jul 2022 13:28:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#954197: gegl: FTBFS (most often on arm64, armhf):
gegl:simple / backend-file times out
has caused the Debian Bug report #954197,
regarding GFileMonitor can deadlock if not cancelled before last unref
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
954197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954197
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gegl
Version: 0.4.18-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://gitlab.gnome.org/GNOME/gegl/issues/226
Control: block 951821 by -1
https://buildd.debian.org/status/fetch.php?pkg=gegl&arch=arm64&ver=0.4.22-2&stamp=1584481529&raw=0
> 1/104 gegl:simple / backend-file TIMEOUT 300.01 s
It isn't trivial to correlate the test's output with which one it is
(this is a legacy test using unstructured output and no particular testing
framework, and I should have made d/rules cat meson-logs/testlog.txt but
didn't), but I don't think it produced any, which means a fairly trivial
GEGL test didn't make any useful progress on these buildds.
https://gitlab.gnome.org/GNOME/gegl/issues/226 appears to be the same thing
on x86_64. I suspect it might be a race condition or otherwise
intermittent: in the past this test also timed out on armel, but my recent
upload worked fine on armel. Perhaps there is something about the ARM
family of architectures that makes this more likely to happen there.
smcv
--- End Message ---
--- Begin Message ---
Version: 2.72.3-1
On Wed, 18 Mar 2020 at 09:37:15 +0000, Simon McVittie wrote:
> On Wed, 18 Mar 2020 at 09:31:50 +0000, Simon McVittie wrote:
> > From the backtrace below it appears that there is a deadlock between
> > threads 1 and 6, which are both waiting for the same mutex. This might
> > be a GLib bug.
>
> Looks like <https://gitlab.gnome.org/GNOME/glib/issues/1941>. The
> workaround, which gegl might be able to use, is to always cancel
> file monitors before their last-unref is reached.
Fixed upstream in 2.72.3 and 2.73.1.
smcv
--- End Message ---
