Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2023/07/24/mutter_43.6-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230724;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230724&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Control: clone -1 -2 -3 -4 -5
Control: retitle -1 mutter: FTBFS: test-framebuffer-get-bits.c:40: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1)
Control: retitle -2 mutter: FTBFS: actor-event-hold test failed with exit status 245
Control: retitle -3 mutter: FTBFS: color-management test: Failed to reset mocked colord state: Timeout was reached
Control: retitle -4 mutter: FTBFS: override-redirect test timed out
Control: retitle -5 mutter: FTBFS: set-parent-exported test: Failed to find mocked color manager system service, Timeout was reached
Control: severity -2 important
Control: severity -3 important
Control: severity -4 important
Control: severity -5 important
Control: tags -2 + unreproducible
Control: tags -3 + unreproducible
Control: tags -4 + unreproducible
Control: tags -5 + unreproducible
Control: block 1043030 by -1
Control: block 1049934 by -1
Control: block 1035092 by -1

This is a long-winded way of saying "some tests failed". The more useful
information for tracking regressions is either "some tests failed" if it's
not possible to extract details, or the details of *which* tests failed.

I can reproduce this, and it's blocking other work on mutter 43. Version
44 in experimental does not seem to have this bug, though.

The assertion failure is:

mutter passed tests when I uploaded it in mid June, so this presumably
must be a regression triggered by changes in some dependency, perhaps
Mesa. Let's use #1042055 for this failure and clones for the rest.

reproducible-builds also has this failure.

There is no obvious error message in the log (the test just exits). There's
a warning, but it's non-fatal and appears in successful tests too. I can't
reproduce this.

"Failed to reset mocked colord state: Timeout was reached". I can't
reproduce this.

Timed out, no additional information in the log. I can't reproduce this.

"Failed to find mocked color manager system service, Timeout was reached".
I can't reproduce this.

Does your archive rebuild infrastructure build other things in parallel on
the same machine, or any other factor like that which could make it more
likely to get stuck / take a long time than a production buildd?

    smcv

Version: 48.3.1-1

This hasn't been seen on official buildds or on ci.debian.net for a while (no
failures observed since 48.2-1) so in the absence of information to the
contrary, I'm going to assume that this was fixed by upstream at some point.

     smcv