Your message dated Wed, 23 Aug 2023 20:39:51 +0000
with message-id <e1qyudr-0027ss...@fasolo.debian.org>
and subject line Bug#1050077: fixed in gtk4 4.12.0+ds-3
has caused the Debian Bug report #1050077,
regarding gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures
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.)
--
1050077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel
gtk4 4.12.0 in experimental has test failures on multiple buildds.
Of those, mips64el and mipsel seem to have the same failure mode:
failure mode:
72/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl
border-one-rounded flipped FAIL
5.47s exit status 1
315/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl / gl opacity-overdraw
FAIL
4.89s exit status 1
316/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl
opacity-overdraw flipped FAIL
4.94s exit status 1
317/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-repeated-gl /
gl opacity-overdraw repeated FAIL
5.05s exit status 1
318/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-rotated-gl / gl
opacity-overdraw rotated FAIL
4.95s exit status 1
319/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-masked-gl / gl
opacity-overdraw masked FAIL
5.02s exit status 1
1406/1464 gtk:reftest / reftest label-sizing.ui
FAIL
19.29s 0/1 subtests passed
1422/1464 gtk:reftest / reftest opacity.ui
FAIL
6.79s 0/1 subtests passed
These are "reftests", which work by rendering the same image in two
different ways and then doing a pixel-by-pixel comparison. Because
Debian buildds do not give us a way to capture test artifacts, the images
are output into the log with uuencode, for example these:
begin-base64 644 testsuite/gsk/compare/opacity-overdraw.png
iVBORw0KGgoAAAANSUhEUgAAAB4AAAAeCAYAAAA7MK6iAAAARklEQVRIie3WMQ4AIAxCUWo8uDev
B7BjYwc+I8tLmAgpjwayJlDgr9lVmYpWJJRP5zc1MDAwMDAwsDFcfq7qI3XHb2o/+AJ0lQS/vZJx
GQAAAABJRU5ErkJggg==
====
begin-base64 644
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.out.png
iVBORw0KGgoAAAANSUhEUgAAAB4AAAAeCAYAAAA7MK6iAAAAS0lEQVRIie3WMQ4AIAhD0aIe3Isb
vACDA5GB35HlJWWpSb5VkFGBAn/Nio5HlopM+Rv8o4Z+PwYGBgYGBgauh8PpY8FGyk6/qvvBF6Er
BMOKG8HLAAAAAElFTkSuQmCC
====
begin-base64 644
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.diff.png
iVBORw0KGgoAAAANSUhEUgAAAB4AAAAeCAYAAAA7MK6iAAAAKklEQVRIie3NoQEAIAzEwGdvZPeG
BUBR3J2MSQKfjFOsZHVO5uUDAAC82WlIAgJv9eZaAAAAAElFTkSuQmCC
====
The way these work is that they are output in sets of three: a reference
image, an actual output, and an artifically-enhanced diff image to
highlight what the difference is. See #1024391, #993550, #1003348 for
previous examples of architecture-specific rendering differences (#1024391
was not on mips*, but has details of how to run individual tests which
might be useful, while the other two were on mips*el).
I haven't reconstructed the actual images for a visual comparison yet.
If the mis-rendering doesn't seem release-critically bad then we'll work
around this by ignoring those particular test failures on mips*el.
mips*el are the only architectures where we are using the softpipe GL
driver (because llvmpipe appears to be otherwise broken there) so that is a
possible root cause.
Having to investigate and work around failing tests in GL-dependent
packages on mips*el is becoming a significant time sink for the GNOME team,
so I would appreciate it if mips porters could fix its llvmpipe so that it
can be back in the same situation as every other release architecture.
smcv
--- End Message ---
--- Begin Message ---
Source: gtk4
Source-Version: 4.12.0+ds-3
Done: Simon McVittie <s...@debian.org>
We believe that the bug you reported is fixed in the latest version of
gtk4, 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 1050...@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 gtk4 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, 23 Aug 2023 16:43:03 +0100
Source: gtk4
Architecture: source
Version: 4.12.0+ds-3
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
<pkg-gnome-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@debian.org>
Closes: 1050077
Changes:
gtk4 (4.12.0+ds-3) experimental; urgency=medium
.
* d/p/tests-Accept-slightly-different-numeric-results.patch:
Replace patch for #1050076 with the version accepted upstream.
This accepts slight numerical differences on all platforms, not
just i386.
* d/rules: Accept minor rendering differences for some tests on mips*.
Presumably these render a bit differently with softpipe.
(Closes: #1050077)
* d/p/debian/reftests-Allow-minor-differences-to-be-tolerated.patch:
Update patch so that when gsk-compare tests are run repeatedly, we
apply the same error-tolerance each time, not just the first time
* d/changelog: Reorder to make the history of unstable linear.
This should avoid the bug tracking system thinking that regressions
found in 4.12.x also affect 4.10.x.
* Merge packaging from unstable
- No further changes, except in the changelog
Checksums-Sha1:
b414aa4ce21b57fe42b7f493f6d6ae91fbc98285 5307 gtk4_4.12.0+ds-3.dsc
83814f9c39e1b3959ddecfc5ed789052e6577d22 3106672 gtk4_4.12.0+ds-3.debian.tar.xz
f68999e82c3c03c6b8358b6669f938a0d01cb54b 18855
gtk4_4.12.0+ds-3_source.buildinfo
Checksums-Sha256:
3ff67ff6be40b99ae380afddf2bba12644522ee1f75372ba08ed1dd91d8c652c 5307
gtk4_4.12.0+ds-3.dsc
246a49e45fffb1bccc2a55cc9e6554feb41e68913f0c6f74e7b7336dd2c8b74c 3106672
gtk4_4.12.0+ds-3.debian.tar.xz
ade4a845450069af16495bf6d9675c506a1d2c20d419e01a897487df3878547e 18855
gtk4_4.12.0+ds-3_source.buildinfo
Files:
5b9947a5244c9ee7529de857e8f12cad 5307 libs optional gtk4_4.12.0+ds-3.dsc
5c235454d2d935c72d217cc393133dc7 3106672 libs optional
gtk4_4.12.0+ds-3.debian.tar.xz
664d4676a69e5281cd20f7695a174682 18855 libs optional
gtk4_4.12.0+ds-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmTmYlQACgkQ4FrhR4+B
TE99cw//be8f6rMig6H3Vy7MMAPfEaDSVVlnEROcQ+2i6jkcSCEo5hZXvKR072GS
tb38iwxvmHwzCj4OD8AKcS4SUMlekalTy0QvDH9g8e86/3WE0EfI4LgMbxzb4v1r
paNua4HYj0bokYSr/5e9CXkUf3ZUH/RXoa7A9WIhTkqpU2XpuJ2EWLEdjXUttie+
6AzXMdC9I0gi3ghdtNbwEG7rIPoGuQwAChyyBFMrBX9I9VvHiJKKkA6SZu86WYPv
uSeGzO6LQKNeCNHz2qgjuN+sSeYTE3OPtBThhaqOLVxqvIwr4L9BhtGLdC+O5XNB
AxNkjxMZaNYcHKcfbDiNPVNUUEisb67xK0j36l37tdtUP8p9X04duGC8zyoVpAII
x2P6ayeFBt6vORv52+NONp3VB2NYjg7qZu/AB3a1JOaijMNzeAhhomcIROETPsNL
gg4Rp9qiQFGUIdt1rcdmP1/zGUOTVylk81v2WJW8ahWvjrcPO8CwqTacX1rRXzXG
M/ynXsNBlNdCG9j6JEc1nVbKTOg0XSmQmDjkfafRmf1Md15odU1Ep0ge/6MYCoqb
PbmgX/41EryJTeklQJ6OOoUZgYGpW6vQDglzryzoyvDLrD7K9qdHD1V5/Y/RLsJw
kE+vJ+jgee0cGwup0aczpPC19j+j5r/TrhwcSYeEXXM5EJ2Li0E=
=3Q7D
-----END PGP SIGNATURE-----
--- End Message ---
