Your message dated Sun, 15 Sep 2024 12:50:31 +0000 with message-id <e1spohz-00acph...@fasolo.debian.org> and subject line Bug#1081515: fixed in weston 14.0.0-2 has caused the Debian Bug report #1081515, regarding weston: 14.x regression: crashes during gtk4 test suite 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 ow...@bugs.debian.org immediately.) -- 1081515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: gtk4 Version: 4.14.4+ds-8 Severity: important Tags: ftbfs help X-Debbugs-Cc: debian-po...@lists.debian.org Until recently, gtk4 was not buildable on any -ports architectures because its build-dependency, weston, was uninstallable. Now it's installable, and building and testing can be attempted. gtk4's test suite is failing on all -ports architectures that have buildds, except for m68k (which I believe builds with nocheck and therefore does not run the test suite at all). The GNOME team is busy with GNOME 47 on release architectures and unlikely to have time to look into this in detail any time soon, but if porting teams would like to have GTK 4 available (it will be increasingly important for desktop architectures in trixie), it would be useful if someone from -ports could investigate. The gtk4 test suite is run in two phases: 1. with --setup=x11, wrapped by "debian/tests/run-with-display x11" which is basically xvfb-run 2. with --setup=wayland, wrapped by "debian/tests/run-with-display wayland" which is intended to be a Wayland equivalent of xvfb-run, using weston in headless mode as the compositor Taking powerpc as my arbitrary example, most tests are passing during the x11 phase. On powerpc, I see a failure in "gtk:gtk / sorter" (unstable and experimental) and in "gtk:gdk / memorytexture" (experimental only) which can be investigated separately; please treat those isolated failures as out-of-scope for the purposes of this bug. However, in the wayland phase, most tests are failing with (fatal) warnings like: (/<<PKGBUILDDIR>>/debian/build/deb/testsuite/gtk/spinbutton:12693): Gtk-WARNING **: 17:54:18.469: Failed to open display weston might be broken on all -ports architectures and functional on all release architectures, but that level of coincidence seems a little far-fetched. So my next theory for this is that something is consistently different about the -ports buildds - perhaps their XDG_RUNTIME_DIR is set up differently? - and that is causing "debian/tests/run-with-display wayland" (or the copy of weston that it runs) to fail? After the failure mode discussed in this bug report has been addressed, it will become more useful to look at individual/isolated test failures (as separate bug reports, please). Based on the status of the less-production-ready release architectures like mips64el and riscv64, I suspect that the most common root cause for individual test failures will be the software OpenGL stack: implementation issues in Mesa's llvmpipe and softpipe, implementation issues in LLVM's old MCJIT and new ORCJIT, and the GTK packaging's choice of whether to mitigate llvmpipe bugs by forcing softpipe (currently done on mips*, riscv*, powerpc, sparc*) or test with llvmpipe (as we do on x86, ARM, etc.). Thanks, smcv
--- End Message ---
--- Begin Message ---Source: weston Source-Version: 14.0.0-2 Done: Dylan Aïssi <dai...@debian.org> We believe that the bug you reported is fixed in the latest version of weston, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1081...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi <dai...@debian.org> (supplier of updated weston package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 15 Sep 2024 14:20:35 +0200 Source: weston Architecture: source Version: 14.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force <debian-x@lists.debian.org> Changed-By: Dylan Aïssi <dai...@debian.org> Closes: 1081515 Changes: weston (14.0.0-2) unstable; urgency=medium . [ Simon McVittie ] * d/p/libweston-noop-renderer-Check-shm_buffer-for-NULL.patch: Add proposed patch fixing a crash while running the gtk4 test suite. Thanks to Jan Alexander Steffens (heftig) (Closes: #1081515) Checksums-Sha1: 956c3451c0264f23b91b9b10765b4b4c4a174b0b 3354 weston_14.0.0-2.dsc f6f368355d8af7aa324bec39ef492cef7d320f4c 26248 weston_14.0.0-2.debian.tar.xz e754630ae0ed19201325663167bac78e7af54c9d 20639 weston_14.0.0-2_amd64.buildinfo Checksums-Sha256: 9cbb992edfe20a145ee4477e9897d41e2f447a13e999739abd832496d289c4e5 3354 weston_14.0.0-2.dsc c6916d4250cf0cbbf7d960535982274368c2f038c35b7c8ba48a09cb8d830272 26248 weston_14.0.0-2.debian.tar.xz 30d2691d271b5f644ac55d3a53deb21d4e0424efb41d4f080175674a374799a4 20639 weston_14.0.0-2_amd64.buildinfo Files: 2f012bdc91313162d8848027c2f614a3 3354 x11 optional weston_14.0.0-2.dsc a35bad6fb7ff28a2f33e78cb9f35e979 26248 x11 optional weston_14.0.0-2.debian.tar.xz b6620f87ac78869031ca5db97394de9e 20639 x11 optional weston_14.0.0-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmbm0vUACgkQYS7xYT4F D1SW0w/8CGNyA0Nd8UqqU0r+9gmS8XtDGar03S972q5jxQJuNX1Byza2Pu1GdXyC t+v9GYTf/cV7phxKb/ZH2PIN09XAX/U+J8CB6cZsNnj5CSewQS8MaL+dQ/aOwpIn XZlVjuwgWjog8/+tLe/ITdQpRt1JyauK/R1Z/VBVXr9++JGYefKa9JuKHV31SHno gwm6+hmSxnBlIVJyyobZ2F8kog8eMr74kXn6+Jzc6CV6Qkc/4jTgchgw/HaqYVVS LuTWcC3A5ADqhxES62qZh/EQzBjb195rH09i/4nhHzntkIVW5OC1Ry+oAus5D3mk e7atwOxUm69gahJQa+1UwJSTn9EzULDC3zQxeLuJe4svW31FxIY5yszC+Rl000aj r34TkytrJ/Rrx1SPk6j8tHXI+CQ8vUp9cpYXVbCFzyUZpWoazU1PmTs/R1FxQ+Dt TcIFk/A48cn5q5LSa2QPAZKmw/2e37SLKAJYQOZfAfFOTjgPM2gchfMDGrLuXxQV XjTRKsSPE4nEioHY8fTuIEPHblaMkUvUzZsxY11FdQvarFZrmeqeI22r9PbBn2dF 9LkCJf1JMnm2xB3Sxylp4sgFGQlOjNEJb6yPtrP5KP/J/TX7DZv3JoxxrkNej1F4 y/vZj5hmFRN7vE76YEhGICknfVTqNldEDAGIrP+eXkFreq674J0= =65Gu -----END PGP SIGNATURE-----
pgpeBM2TOaVXk.pgp
Description: PGP signature
--- End Message ---
