-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xb-self-test intermittently hang #59
Comments
the
is super weird. I wonder if running it in the same environment using valgrind would show anything bad. |
Here is the relevant output of a failed run under valgrind (and here is the full log):
|
So meson SIGKILLd the process after 300 seconds. How long does it take on a successful build? It's not getting scheduled on a machine that's 100% loaded or something? |
That's a successful run in a groovy chroot on my laptop, and CPU usage seems irrelevant (I can get successes and failures both at rest and under heavy load − locally building firefox):
Note that meson is not involved here, I'm running the tests from the debian package, which simply invoke |
I'm out of ideas I'm afraid. |
btw I saw this too and got a backtrace (line numbers are from 0.1.15-2 as in Debian/Ubuntu). It appears to be deadlocking on a monitor:
|
@pwithnall am i doing anything dumb? |
I think it's probably the same as https://gitlab.gnome.org/GNOME/glib/-/issues/1941 - testing the suggested fix there now |
Yeah it’s probably that. If anyone wants to fix the GLib bug, please be my guest 🙂 |
GFileMonitors currently need to be explicitly cancelled when they are unreffed, otherwise they can deadlock due to the GLib-internal worker thread also holding a strong reference to the monitor. For full details, see: https://gitlab.gnome.org/GNOME/glib/-/issues/1941 Closes hughsie#59
Yeah that works, see #83, thanks! |
GFileMonitors currently need to be explicitly cancelled when they are unreffed, otherwise they can deadlock due to the GLib-internal worker thread also holding a strong reference to the monitor. For full details, see: https://gitlab.gnome.org/GNOME/glib/-/issues/1941 Closes #59
The autopkgtests for libxmlb in Ubuntu failed a couple of times recently on amd64, and I managed to reproduce the failure by running the test in an infinite loop.
I'm attaching a full log. The test always appears to hang after
ok 14 /libxmlb/builder{ensure}
, and it printsExecuting: libxmlb/libxmlb.test
every 5 seconds until it times out after 5 minutes.This is on Ubuntu groovy (amd64).
The text was updated successfully, but these errors were encountered: