Your message dated Tue, 05 Nov 2024 15:07:21 +0000 with message-id <e1t8l9n-007cz7...@fasolo.debian.org> and subject line Bug#1086552: fixed in mutter 47.1-2 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-2 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: Tue, 05 Nov 2024 12:25:13 +0000 Source: mutter Architecture: source Version: 47.1-2 Distribution: experimental 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-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. Checksums-Sha1: 390353c2d9108ffbf67668019604705d610d6c8e 4621 mutter_47.1-2.dsc ed16c0ac6b84b43bd211e67964627d319955a108 89652 mutter_47.1-2.debian.tar.xz cb5be733a561ad98b12081ae02088fe8a60c129f 20379 mutter_47.1-2_source.buildinfo Checksums-Sha256: 9b790596e0d32a0b947df283a92a74c671725ea43159dea0e1db6f292dc1b025 4621 mutter_47.1-2.dsc c8974283bea916b2a40cdbc02722415830519c7e584f7ec60ae49c0c1a65fc42 89652 mutter_47.1-2.debian.tar.xz f3afe9984f33a4677a2ad989001d515a9a940c1268b799fa1236e3854eba09ba 20379 mutter_47.1-2_source.buildinfo Files: 1ab2403dc0f2d9226fcebe08f1c59392 4621 x11 optional mutter_47.1-2.dsc 68ed33ed6d5e1d00ace9ca6bbe15c0d8 89652 x11 optional mutter_47.1-2.debian.tar.xz 6f3b3fb28efc084cf33cafdfcf6e1ea8 20379 x11 optional mutter_47.1-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEegc60a5pT6Jb/2LlI1wJnT6zMHYFAmcqMq8ACgkQI1wJnT6z MHZtPg/+Mx4bYHOX8kzQ/y6INXkg5UXyxIZ3chQkMXlnJQba6wpJNbbA/D06Mwcq g1EUgy9Cz2YcCDgKwALYY6uLnEGWxc7jGOACknLM9IABn6JC1AEuUL4ArO+38LyJ rSxqH4YdtZzOuwzkkPPQyMtYkT8CrKxXfqVC4c5E16lS5t33542J7Qi+0sOJ9nnS hlP4xdfu0LA0/784GgFcvt+qffpAiwhTGsGpA6uUnFdMepVc5QElKr+LbSwSwVHB yv94XZ8++G0Z/wZGl7yPuwmiT1OI0zr0TaoPIT3qOmExtC0TnaPf2rie7tKoWpwA fSF6mWseSZbOcOBuhaOQgNrIEoJdn8uZU9ysPg5EPCb2iYHcV68Q4zE0A7/iyXXN JhsugNHJYIikIlOn9DqsE/LysChT4g3x+LpGTRE38nXNLk6+wy3Ug7u1s3Jib4yI EDKp4ySlmQVJiwrA91GMrNLGb3uw5Dgjmow0t2oR+xIDjlCq3PtwhiLuWz963Dx8 h9nwLdAqlypAszJse1pFq/bLGF0IBZ6cvTo+Ox+B9qrczWEF8EZ7nqsGsOHPFXn5 iDsMt/sNBxkAsDiIrxFe5pJ54j5dFZWGHX5R72Jkk0O4xUlomTMcrjNME/+zcOB0 wbuIAxmvQz8lJm8GcpiIxez7BJxPc+9zdNJePlvz7RCfbwUz0fo= =CBQa -----END PGP SIGNATURE-----
pgpIYdwz2QX_s.pgp
Description: PGP signature
--- End Message ---
