Debian Bug report logs - #1086552
mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame

Date: Fri, 1 Nov 2024 10:43:24 +0000

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

Message #8 received at 1086552-submitter@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <noreply@salsa.debian.org>

To: 1086552-submitter@bugs.debian.org

Subject: Bug#1086552 marked as pending in mutter

Date: Tue, 05 Nov 2024 08:46:53 +0000

Control: tag -1 pending

Hello,

Bug #1086552 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/mutter/-/commit/04b79a1d36500d070a2fa5a650901d09648050b7

------------------------------------------------------------------------
d/patches: 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
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1086552

Message #15 received at 1086552-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1086552-close@bugs.debian.org

Subject: Bug#1086552: fixed in mutter 47.1-2

Date: Tue, 05 Nov 2024 15:07:21 +0000

[Message part 1 (text/plain, inline)]

Source: mutter
Source-Version: 47.1-2
Done: Simon McVittie <smcv@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 1086552@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@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 ftpmaster@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-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@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-----

[Message part 2 (application/pgp-signature, inline)]

Message #20 received at 1086552-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1086552-close@bugs.debian.org

Subject: Bug#1086552: fixed in mutter 47.1-4

Date: Wed, 06 Nov 2024 16:51:22 +0000

[Message part 1 (text/plain, inline)]

Source: mutter
Source-Version: 47.1-4
Done: Simon McVittie <smcv@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 1086552@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@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 ftpmaster@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-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@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-----

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.