Your message dated Wed, 06 Nov 2024 16:51:22 +0000 with message-id <e1t8jfa-00cvcc...@fasolo.debian.org> and subject line Bug#1086552: fixed in mutter 47.1-4 has caused the Debian Bug report #1086552, regarding mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame 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.) -- 1086552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mutter Version: 47.1-1 Severity: serious Tags: ftbfs experimental Justification: fails to build from source (but built successfully in the past) mutter failed to build from source on several architectures, including 'all', with this failure in the "mutter:clutter+clutter/conform / timeline" test-case: > 1..1 > # Start of timeline tests > Without delay... > 3: Doing frame 10, delta = 0 > 2: Doing frame 0, delta = 0 > 1: Doing frame 0, delta = 0 > # libmutter-INFO: Acquired name org.gnome.Mutter.InputMapping > # libmutter-INFO: Acquired name org.gnome.Mutter.ServiceChannel > 3: Doing frame 8, delta = 261 > 3: Marker 'start-marker' (1666) reached, delta = 261 > 2: Doing frame 2, delta = 261 > 1: Doing frame 2, delta = 261 > 1: Marker 'start-marker' (0) reached, delta = 261 > 3: Doing frame 8, delta = 100 > 3: Marker 'baz' (1333) reached, delta = 100 > 2: Doing frame 2, delta = 100 > 2: Marker 'bar' (333) reached, delta = 100 > 1: Doing frame 2, delta = 100 > 3: Doing frame 7, delta = 100 > 2: Doing frame 3, delta = 100 > 1: Doing frame 3, delta = 100 > 3: Doing frame 7, delta = 100 > 2: Doing frame 3, delta = 100 > 1: Doing frame 3, delta = 100 > 3: Doing frame 6, delta = 100 > 2: Doing frame 4, delta = 100 > 1: Doing frame 4, delta = 100 > 3: Doing frame 5, delta = 100 > 2: Doing frame 5, delta = 100 > 1: Doing frame 5, delta = 100 > 3: Doing frame 5, delta = 100 > 3: Marker 'foo' (833) reached, delta = 100 > 2: Doing frame 5, delta = 100 > 1: Doing frame 5, delta = 100 > 1: Marker 'baz' (833) reached, delta = 100 > 1: Marker 'bar' (833) reached, delta = 100 > 1: Marker 'foo' (833) reached, delta = 100 > 3: Doing frame 4, delta = 100 > 2: Doing frame 6, delta = 100 > 1: Doing frame 6, delta = 100 > 3: Doing frame 4, delta = 100 > 2: Doing frame 6, delta = 100 > 1: Doing frame 6, delta = 100 > 3: Doing frame 3, delta = 100 > 2: Doing frame 7, delta = 100 > 1: Doing frame 7, delta = 100 > 3: Doing frame 2, delta = 100 > 2: Doing frame 8, delta = 100 > 1: Doing frame 8, delta = 100 > 3: Doing frame 2, delta = 100 > 2: Doing frame 8, delta = 100 > 1: Doing frame 8, delta = 100 > 3: Doing frame 1, delta = 100 > 2: Doing frame 9, delta = 100 > 1: Doing frame 9, delta = 100 > 3: Doing frame 1, delta = 100 > 3: Marker 'near-end-marker' (166) reached, delta = 100 > 2: Doing frame 9, delta = 100 > 1: Doing frame 9, delta = 100 > 1: Marker 'near-end-marker' (1500) reached, delta = 100 > 3: Doing frame 0, delta = 100 > 2: Doing frame 10, delta = 100 > 1: Doing frame 10, delta = 100 > 3: Doing frame 0, delta = 100 > 3: Marker 'end-marker' (0) reached, delta = 100 > 3: Completed > 2: Doing frame 10, delta = 100 > 2: Completed > 1: Doing frame 10, delta = 100 > 1: Marker 'end-marker' (1666) reached, delta = 100 > 1: Completed > FAIL: missed 1 frame for timeline 1 > ** > Clutter-Conform:ERROR:../src/tests/clutter/conform/timeline.c:281:timeline_base: > assertion failed: (check_timeline (timeline_1, &data_1, TRUE)) If this is operating in real-time, then I think this test might need to be disabled or marked as flaky for buildd purposes: on an un-loaded developer machine with a real GPU and other nice amenities, we might be able to assert that the deadline for a frame is never missed, but on a buildd that is set up for batch processing, rendering in software and potentially running other things in parallel, I don't think that assertion is realistic. It might also be pragmatic to disable the tests when we are only doing an Architecture: all build (like we do in glib2.0), so that those always succeed, even if some builds for specific architectures fail. smcv
--- End Message ---
--- Begin Message ---Source: mutter Source-Version: 47.1-4 Done: Simon McVittie <s...@debian.org> We believe that the bug you reported is fixed in the latest version of mutter, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie <s...@debian.org> (supplier of updated mutter 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: SHA256 Format: 1.8 Date: Wed, 06 Nov 2024 15:06:02 +0000 Source: mutter Architecture: source Version: 47.1-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers <pkg-gnome-maintain...@lists.alioth.debian.org> Changed-By: Simon McVittie <s...@debian.org> Closes: 1086552 Changes: mutter (47.1-4) unstable; urgency=medium . * Team upload * Release to unstable . mutter (47.1-3) experimental; urgency=medium . * Team upload * d/p/workarounds/Mark-several-additional-tests-as-flaky.patch: Treat timeline and timeline-interpolate tests as flaky. Both of these tests make assertions about frame deadlines that are not reliable on the buildds. - d/p/workarounds/tests-Don-t-check-for-missed-frames-during-automated-buil.patch: Drop, no longer necessary with the above change * d/libmutter-15-0.symbols: Remove unnecessary revision from a symbol. meta_session_manager_new_for_fd() is present in the upstream codebase, therefore in any package based on 47.0. * d/copyright: Update filename of vx239-calibrated.icc * d/control: Make mutter-common-bin Multi-Arch: foreign. Its only interface is via running executables. . mutter (47.1-2) experimental; urgency=medium . * Team upload . [ Daniel van Vugt ] * d/p/debian/Support-Dynamic-triple-double-buffering.patch: Update the triple buffering patch for 47.1, using the official maintenance branch . [ Simon McVittie ] * d/p/workarounds/tests-Don-t-check-for-missed-frames-during-automated-buil.patch: Don't assume that autobuilders will meet frame deadlines. The upstream test suite assumes a reasonably low-latency system with a GPU, but that doesn't describe an autobuilder. (Closes: #1086552) * d/rules: Only run the test-suite for architecture-specific builds * d/rules: Use /proc/self/fd/2 in preference to /dev/stderr. Not all container technologies provide the latter. * d/rules: Treat x11-test.sh as flaky. It doesn't seem to add a lot of test coverage, and is intermittently failing for me when run under sbuild in a bookworm VM. . mutter (47.1-1) experimental; urgency=medium . * Team upload * New upstream release * Rebase patch series * d/control: Bump libgudev-1.0-dev dependency as per meson.build Checksums-Sha1: 431b4cc6558dbf36c0424c2e161cf85599e14be7 4621 mutter_47.1-4.dsc cf532b36e239a6cc7b4636a0f9f58eecb5ce46fa 89696 mutter_47.1-4.debian.tar.xz 2b1a1bafacbb0c90613362ec17885c2856f9c1c4 20673 mutter_47.1-4_source.buildinfo Checksums-Sha256: 2dd41b47f6b7938217cfa67b642393843160021b2e898af50544dd6fd5986ea0 4621 mutter_47.1-4.dsc 7af45647f9f1da92f101b9782fca4b28833a79702ea521b4ce38fc061e3dad6e 89696 mutter_47.1-4.debian.tar.xz 2ba31c1ea9fd0655a62e6218f2246fe2e404e0cf9be18df0196ea26c6a1fb067 20673 mutter_47.1-4_source.buildinfo Files: 6dae7c55d56facf1c6aa539479d205ab 4621 x11 optional mutter_47.1-4.dsc 26b5ae9a8b5580ee156ce9fe6d6bcd78 89696 x11 optional mutter_47.1-4.debian.tar.xz f8a44cd4ed31837ed74344fdc6427285 20673 x11 optional mutter_47.1-4_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEegc60a5pT6Jb/2LlI1wJnT6zMHYFAmcrmQEACgkQI1wJnT6z MHbWHQ/8D7kxW+ARWhICm7ZsssfBwwVbanUJV9lh4KJZWjJ7BvGcpYjxSHtMC2JH xDAgk00HaLr333d54D9kzTKPAlkWCOGDV+gLh7/qhJo+KN/lY9zWAIE2ZqINh5Lr 0CsvnsZ+ETsQ+2bA19MNBEWMQoKQPoHVEoxEaK/Q9iGKK1gGhjL+2D7L05a6dkIu 8ZBpJLCRuZyMtzFbFqSVXOrfnVIPt4W2iTGjBxR/82v91D8S21+ktd+b/e++XYgq O/EUMRW9KoamRJq0BgwfTofoJyg7Hv2pMm99WD+us66Ysxoe/N9VJNQT5kO5JR38 iET/6w9hdsxFVH+IQqPddG1urWibGmH+CKGgKdHPjzsZXFCyB+pjDu/iIEO3VN/R YSbhswTNiiLzw/9eFTrXwwHQLAoSExwibWdUfqsKqTs3DQvFX3mRES1z9Gzbl8Z6 qMWIhx6RkKjSRLjy6dB0y1A2Z5ZI66AwL7oPYMgawud9d1qcyjH8+250rNmA+lH+ DgLoKo4IjZTAkzKUNPyp/TzreSdEM3NgRYk3NR3Y+9xhvjt7siz+ILWL+YmlzNpx w36WHFILFS7GXcfU5F0Ok3ordIH2Xiye2MtK+BcOT/Z3L263HwXJMVGjWn8N/Qn9 wwMpEN9mg8k9b9GjHEQtQEq9xxgxMjt7pslNrd8FOPYECPPy3zI= =V+2u -----END PGP SIGNATURE-----
pgprnZ1VCMlyK.pgp
Description: PGP signature
--- End Message ---
