#1064704 gtk4: FTBFS: one run of gtk:tools / validate test failed

#1064704#5
Date:
2024-02-25 19:37:28 UTC
From:
To:
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/2024/02/24/gtk4_4.12.5+ds-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240224&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.

#1064704#12
Date:
2024-02-26 12:49:54 UTC
From:
To:
Context for Mesa maintainers: gtk4 passed its build-time tests on
2024-01-29, but is now failing in a test rebuild. I can reproduce this,
and I think it's a regression triggered by Mesa changes (see also
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10293 upstream).

Unfortunately, the only log output for this was:

1..9
not ok 1 invalid1
not ok 2 invalid2
not ok 3 invalid3
not ok 4 invalid4
not ok 5 invalid5
not ok 6 valid1
not ok 7 valid2
not ok 8 valid3
not ok 9 valid4

I notice that many tests have this stderr output:

Looking at the implementation of the testsuite/tools/validate test,
the way it works is: run GTK's validator against a valid or invalid
input, compare the resulting stderr with what was expected, and fail if
they differ. I think the reason why it's failing is that it's seeing this
extra stderr from Zink.

Obviously, this is quite fragile, because anything that emits a diagnostic
message can break it; but I also don't see any way for GTK upstream to get
the behaviour they want ("assert that the validator produces the messages
that we think it should") without that fragility.

Could this output to stderr in Zink perhaps be reconsidered upstream?

    smcv

#1064704#19
Date:
2024-02-26 15:35:06 UTC
From:
To:
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 1064704@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 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 26 Feb 2024 13:12:57 +0000
Source: gtk4
Architecture: source
Version: 4.12.5+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Closes: 1064704
Changes:
 gtk4 (4.12.5+ds-3) unstable; urgency=medium
 .
   * d/rules: Always use Mesa software rendering during the build.
     We do not expect autobuilders to have hardware GPUs available, and
     forcing software rendering makes build-time tests run by developers
     consistent with build-time tests run on autobuilders.
     This also avoids using Zink, which is not usually available on
     autobuilders either (because there is no hardware Vulkan driver),
     but produces messages on stderr that will make some of our tests fail.
     (Closes: #1064704)
Checksums-Sha1:
 2e457ccc061161ef74d274052986880ea69ecef8 5382 gtk4_4.12.5+ds-3.dsc
 7138269531b2c5d4fb62d8383cf926845ac990fb 3601824 gtk4_4.12.5+ds-3.debian.tar.xz
 97ed8f3ed5d07e6565077fe2075ab5935a23c613 20509 gtk4_4.12.5+ds-3_source.buildinfo
Checksums-Sha256:
 f7ead806059a19c9854b4df0991834f6fc4f51c8b850e419bc7032c369667797 5382 gtk4_4.12.5+ds-3.dsc
 d99b80918b763071c3986698e57b27917ceee651ab29b2d7671210aa902d2133 3601824 gtk4_4.12.5+ds-3.debian.tar.xz
 435da4d6a6923dee02133325ef974759400b59d1b808b5cf923d167e5f360edb 20509 gtk4_4.12.5+ds-3_source.buildinfo
Files:
 15a2640fc022f9ac3634fb90eeb26289 5382 libs optional gtk4_4.12.5+ds-3.dsc
 dac05bb6973c4027ff7e6beee8420f04 3601824 libs optional gtk4_4.12.5+ds-3.debian.tar.xz
 660ba8ead9edd17b10e0883ff4b97b84 20509 libs optional gtk4_4.12.5+ds-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmXcrUoACgkQ4FrhR4+B
TE8Hxg//ae1OcjZtWXC3g8BYHMwJfSLjS67wWUFRsFK7aGaPxBczGdwQvAYTAEy0
dWt2o388LfRPT0bZyK7py5llKsBLUPAaBJgpjUP8amipt43ylE72DrPgfblEJxgE
0kkcFDKrDJVZfMI1dWugLBFFstJrPjEmOilHjACLra7QXPc4w8NpMazO3T58zvdT
NfctWSBwp4y1an1ytZOpf9PdvltqlyTmfx+6h2FlTQxeILGjXJrZugcw7cKZbsFn
/qqDljrbAmwqSI6jZULav5OsYNhSbCif7M/WVWJHAIm+H/cdsIlQx3FyagePHj4a
3DwP8mjdNrM9vddEOzLEQ4iw3/7kyiMSdcRGWrB3DIQiWKloUOG+43+z3xe9hvrA
DzWf8hU0FGqbQzbpCW6VonLD9L8sh93b7gZe/fZbfqMgbxhbkrw7AW52Xm9vA5MK
+shVC+/wN+0G2Hog7qW8ujPL0aMTlmtiKFa5K1anGWJz1c5GkcYOXmIz/3Kw4svi
u12w1me7vRRMhX0c69M4yVjyB/imrrVHzQP0H1zHugpsVS/O7WE5CgFeOhJg9MVT
ix35sp33TlPqJMY6iQPe9948qDh2/scIjr0LTjmw29EmRfc4cbsDIae4UHgrYH9d
RdRUVqg6krJgmyk+Ya3MAvHmg59HnT+9zIMT+dnhj76RC1l2H34=
=5bB3
-----END PGP SIGNATURE-----

#1064704#24
Date:
2024-02-29 09:12:53 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
mesa, 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 1064704@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen <tjaalton@debian.org> (supplier of updated mesa 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)
Format: 1.8
Date: Thu, 29 Feb 2024 09:22:00 +0200
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaalton@debian.org>
Closes: 1064704
Changes:
 mesa (24.0.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * clc-build-fix.diff: Dropped, upstream.
   * fix-zink-logging.diff: Don't log to stderr when zink fails to load.
     (Closes: #1064704)
Checksums-Sha1:
 5c92940bc02a096cd9399375a72928dc74842c1b 5622 mesa_24.0.2-1.dsc
 2a8f6a1f1292b4dd5e7ebffd8bc229aca2f01bd0 32818342 mesa_24.0.2.orig.tar.gz
 c69b405358f2c9b6489a650f0abfc21c8aa88edf 117876 mesa_24.0.2-1.diff.gz
 fafc86172875006ae8774e2f14f0770db4c0c352 10271 mesa_24.0.2-1_source.buildinfo
Checksums-Sha256:
 8b1bf735a33474b6e07fb6a8ef2760bb5b0615e7bf79195cfd84cabd75af2d5a 5622 mesa_24.0.2-1.dsc
 27cf21fccfca35c030d9f9dbc78125c7927aac57827a8b63229083f808ab1335 32818342 mesa_24.0.2.orig.tar.gz
 e7b20a15baecc3857c68a389563e2ea2023c9ad6388731bc4fb1ffaac98040d0 117876 mesa_24.0.2-1.diff.gz
 0e8f336f452f55578af53fea16798f0b7871b990427b65c517c7d0e891d74dab 10271 mesa_24.0.2-1_source.buildinfo
Files:
 807537ca681b0429a6e0cefcb67c9f62 5622 graphics optional mesa_24.0.2-1.dsc
 89df790a56320ebd362cb184340931b0 32818342 graphics optional mesa_24.0.2.orig.tar.gz
 a8aa1c833661713a87190754f519e07f 117876 graphics optional mesa_24.0.2-1.diff.gz
 91a91ecd5c333e950ffa2938bf487a3b 10271 graphics optional mesa_24.0.2-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmXgMKwACgkQy3AxZaiJ
hNz3bA/+PYHfrf9//qaT5JVSLaMCdtgFYSIX1B53JCbBNY5XcPEtQn7yXHRCS8uD
fAh3matQsBSlGC6fN/rV4DMM1sEHyem79mQuCtpnZRVKmGXcdVnFnhsy/NK01G5T
iRjE6eSF0huSr1KNidRTDryvFqP3l/uqMAwAE+7w5HLtQ9px/m22dUhCdx1CxgNG
Th3O8AfxW1CnPWP6kJgJYwX4GcKkM6ug1jNjTiFt/YbTOze1BgKzsNVZ2dX4Vc7l
BQ0OUjJ/bdac5J2OkRMU/M8JNsn2e3BxowJ6OX/vUQPlBbYFEiDLwyvpEqfNWtZr
r6SObRf8uUinGyqdZLJ5vKbb4g8XB5g0hW/VagUYYnitrFoScjj4DLUbwdqkfawp
rtfgwpoDZ0vWXD0aCRgSBYizb9rfvZVv8b8J4vnPCSGPs30g0vTOOCkqUnfxbbQ7
FfRqtRM7/kCVT13JSqbzvRCXAGNQMng/OdXmX8df2z1YF2XSVWrHIT/IRl0CPOxl
MABJyfHa42HBDNE6lF266d4zQCSB/1ga1sdCvnPAkMk9X4SWeGGnhm+HgxVs+5OK
2k4oum1qLqiMIPdpvzt0aspigr+Q1fXAR5yx3mQV1KKWxipDS+Y1OScx04ZbOsuI
3m22511yv2yWturxw5mZWHilnfYPbMcQt8PtSDOf/O1EXThPfSk=
=vca9
-----END PGP SIGNATURE-----