https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6274/steps/12/logs/stdio Failed ptests: {'glib-2.0': ['glib/gsubprocess.test']} qemux86-64-ptest alma9-ty-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6222/steps/12/logs/stdio qemux86-64-ptest fedora38-ty-4
# /gsubprocess/exit-status/trapped summary: Test that exit status is reported correctly for ptrace()d child processes # Bug Reference: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3433 ** GLib-GIO:ERROR:/usr/src/debug/glib-2.0/2.78.3/gio/tests/gsubprocess.c:2046:trace_children: assertion failed (ptrace (PTRACE_CONT, pid, NULL, 0) >= 0): errno 3: No such process not ok /gsubprocess/exit-status/trapped - GLib-GIO:ERROR:/usr/src/debug/glib-2.0/2.78.3/gio/tests/gsubprocess.c:2046:trace_children: assertion failed (ptrace (PTRACE_CONT, pid, NULL, 0) >= 0): errno 3: No such process Bail out! FAIL: glib/gsubprocess.test (Child process killed by signal 6)
Probably a sub-process/strace race. We have updated glib a few times since this was last seen.| Assume fixed.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/747/steps/12/logs/stdio qemuarm64-ptest ubuntu2004-vk-arm2 Reopening.
Happened with glib 2.82.4 but for some reason the log that I download isn't the one that fails.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2391/steps/13/logs/stdio qemux86-64-ptest fedora41-vk-1
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/2549/steps/13/logs/stdio qemuarm64-ptest ubuntu2204-vk-arm1
The test timeout for glib-2.0 tests was doubled in: https://git.openembedded.org/openembedded-core/commit/?id=f634098ed6c5674d81028a7ea8e18a7a93a77fab Neither of the glib-2.0 intermittent test failures has been seen for at least a month, so let's close this. We can reopen it if it starts appearing again.