[continued from previous message]

X-Spam-Status: No, score=-109.2 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
HAS_BUG_NUMBER,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
USER_IN_DKIM_WELCOMELIST,VERSION autolearn=ham autolearn_force=no
version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 150; neutral, 150; spammy,
0. spammytokens:
hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <[email protected]>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:55052)
from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=stravinsky.debian.org,EMAIL=[email protected] (verified)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.96)
(envelope-from <[email protected]>)
id 1uZ4O3-007Dgf-08
for [email protected];
Tue, 08 Jul 2025 09:13:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org;
s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version:
References:Message-ID:Subject:Cc:To:From:Date:Reply-To:
Content-Transfer-Encoding:Content-ID:Content-Description;
bh=SbaxbuHN1ywp01WJi9ooD7OkD1NO4v7iw0ZAFaGa50k=; b=oz7Gpzfb3t/+0Pb0CYaBzIShU1
mkA9RNkrCIM+4WcdtOQ7WqGqNgoHTJKuCjhd9sslh0e05YxykklI8qz6qEU069ceaz5trJlEbyyqT
+O8snfQ1cjyK2BXJu7caVzw+rQ0d8yV5VFNylyw5DGpEefHuqjNuxQtHsbPtzKnsrABSoCFGyMN1a
Eqtz2iN5Fo75p872LW2pmER+lnmN3BpKrCrpUQD8oXxkREzPtRvn3PVH56hydeE58kVJPM/hBejpc
H3A9iE3ZA2neo8c2i8TwKM8AYmvlt+6AgFOZj+7Z6jiD79kZlcNulgG2bnWO2pTkOUHW+pPEjLgXu
LlVBdJQg==;
Received: from authenticated user
by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.94.2)
(envelope-from <[email protected]>)
id 1uZ4O0-00DVvX-Mn; Tue, 08 Jul 2025 09:13:13 +0000
Date: Tue, 8 Jul 2025 10:13:11 +0100
From: Simon McVittie <[email protected]>
To: [email protected]
Cc: Luca Boccassi <[email protected]>, Santiago Vila <[email protected]> Subject: Re: Bug#1093969: mutter: autopkgtest are flaky
Message-ID: <[email protected]>
References: <CAMw=ZnQD3qEdab=kQoanmYqW9bKQebRfa-=[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <CAMw=ZnQD3qEdab=kQoanmYqW9bKQebRfa-=[email protected]>
X-Debian-User: smcv

Version: 48.3.1-1

On Fri, 24 Jan 2025 at 11:30:01 +0000, Luca Boccassi wrote:

mutter autopkgtest are flaky and often fail and require multiple
manual reruns to let unrelated packages migrate, especially on >armhf/armel/ppc64el.

The main root cause of test failures in mutter seems to have been
"In pixman_region32_init_rect: Invalid rectangle passed" (#1077800). We
are no longer seeing this failure mode, and I think that's because of mutter!4039 upstream (48.3.1-1) or possibly some other upstream bug fix.

Another intermittent failure was "(EE) could not connect to wayland
server" which we have not seen since 48.2-1, so hopefully that is
another failure cause that has subsequently been fixed.

There have been no failures observed for release architectures on
ci.debian.net since 48.2-1 back in April, so I think whatever was the
root cause for the flaky autopkgtest must have been fixed - either fully
fixed, or at least, made substantially less likely.

(I'm not counting the more recent failure https://ci.debian.net/packages/m/mutter/unstable/loong64/61423775/ on
loong64 as a problem with mutter itself, since it was an installability
issue during architecture bootstrapping rather than anything that can be
blamed on mutter.)

The most recent failure of the same test suite on the buildds (only
looking at release architectures) was 48.1-1 on amd64, which, again,
failed with symptoms matching #1077800. This appears to be fixed, or at
least a lot less likely, in newer upstream bugfix releases.

If similar test failures are still reproducible, please report a
separate bug describing the failure observed, with logs and whatever
details of the test system are available - we can't debug or fix a
failure that we can't observe. Ideally different failure modes should
have different bugs, similar to #1077800, #1050008 and so on, so that we
can keep track of what is fixed and what is still an issue.

For the build-time tests, any test failures will appear in the build log
as usual.

For the autopkgtests, currently the test log only provides a summary of
the test-cases that failed (for example in https://ci.debian.net/packages/m/mutter/testing/armel/61424275/ the
single failure was mutter-16/surface-scale-tests.test) and the detailed
result is in the similarly-named file
mutter-16_surface-scale-tests.test.txt in the $AUTOPKGTEST_ARTIFACTS
(available on ci.debian.net as artifacts.tar.gz).

Thanks,
smcv

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)