I have a long standing (1.5 years) problem with https://codereview.qt-project.org/c/qt/qtbase/+/427313 that the CI hangs on so-called "cmptest". Previously the CI just reported that timeout has happened and I had no idea what exactly happened. Asking reviewers to get a backtrace to see where it hangs led to radio silence. Good news is that the CI became better on this in those 1.5 years and gives the following backtrace at least:
agent:2024/04/12 13:42:11 build.go:404: 352: #0 0x00007f260ca63bcf in __GI___poll (fds=0x7ffc92393898, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 agent:2024/04/12 13:42:11 build.go:404: 352: #1 0x00007f260b97b7e2 in () at /lib/x86_64-linux-gnu/libxcb.so.1 agent:2024/04/12 13:42:11 build.go:404: 352: #2 0x00007f260b97beb1 in () at /lib/x86_64-linux-gnu/libxcb.so.1 agent:2024/04/12 13:42:11 build.go:404: 352: #3 0x00007f260b97cea6 in xcb_wait_for_reply64 () at /lib/x86_64-linux-gnu/libxcb.so.1 agent:2024/04/12 13:42:11 build.go:404: 352: #4 0x00007f260c7f431c in _XReply () at /lib/x86_64-linux-gnu/libX11.so.6 agent:2024/04/12 13:42:11 build.go:404: 352: #5 0x00007f260c7d9888 in XInternAtom () at /lib/x86_64-linux-gnu/libX11.so.6 agent:2024/04/12 13:42:11 build.go:404: 352: #6 0x00007f2606b453d8 in gdk_x11_atom_to_xatom_for_display () at /lib/x86_64-linux-gnu/libgdk-3.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #7 0x00007f2606b39c29 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #8 0x00007f2606b3b191 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #9 0x00007f2606b3ed28 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #10 0x00007f2606b04a99 in gdk_display_get_event () at /lib/x86_64-linux-gnu/libgdk-3.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #11 0x00007f2606b3ef46 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #12 0x00007f260c6c9d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #13 0x00007f260c71f258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 agent:2024/04/12 13:42:11 build.go:404: 352: #14 0x00007f260c6c73e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Still, this backtrace doesn't have debug symbols and doesn't really help. Can I get a better backtrace from the CI somehow, with debug symbols for glib, gtk3, Xlib and xcb? Who and how should I contact for that? -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
