Debian Bug report logs - #1057562
gcr4: FTBFS: failing tests

Display info messages

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

From: Santiago Vila <sanvila@debian.org>

To: Debian BTS <submit@bugs.debian.org>

Subject: gcr4: FTBFS: failing tests

Date: Tue, 5 Dec 2023 23:05:42 +0100

Package: src:gcr4
Version: 4.1.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_configure -- \
	-Dauto_features=enabled \
	-Dgtk_doc=true \
	-Dintrospection=true \
	-Dssh_agent=false -Dgtk4=false \
	-Dsystemd=disabled
	cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 -Dauto_features=enabled -Dgtk_doc=true -Dintrospection=true -Dssh_agent=false -Dgtk4=false -Dsystemd=disabled
The Meson build system

[... snipped ...]

# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.11: /org/gnome/keyring/Prompt/p8
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=I5vgW6S2rwRRFsyYj6xl4OGLJ+vwi5NdSE6pNOR9BRAWE4BpiwcfiTHf9dKlSAn8TUZ8sYgQ9ipmMvGEBzI8VlZLae7hjslQVDT11PTGhUPFNEWycpYxTH09US0cOiJKx+Ks/3313pwWYXh1dFanPuXqLVk5lhvYT9TO0FBLXAJRWzSfu7QTnUg8hwbmxePtGqBDocjybr0UYWgn6Ca/0mEk8UnBdjW4M2uaXo0sVBuqUx94SxOHG6HUJplOyFXc\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=I5vgW6S2rwRRFsyYj6xl4OGLJ+vwi5NdSE6pNOR9BRAWE4BpiwcfiTHf9dKlSAn8TUZ8sYgQ9ipmMvGEBzI8VlZLae7hjslQVDT11PTGhUPFNEWycpYxTH09US0cOiJKx+Ks/3313pwWYXh1dFanPuXqLVk5lhvYT9TO0FBLXAJRWzSfu7QTnUg8hwbmxePtGqBDocjybr0UYWgn6Ca/0mEk8UnBdjW4M2uaXo0sVBuqUx94SxOHG6HUJplOyFXc\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=233ug6pl2hz5Qx0iLQjtP7cskjda9453w9q3PeLo4dAH7LT/RpdTYX68g/4/jdM6jEhIFqzuxTzKcNBmpNfOIgG7peVVnt8WfU06uqMDNZeQgi56awwhv8btRZN4J8b0dcKK36ozVZissrgsJd87SOiSqluDpxJ7gdX7gSinh7P6eYVp4TdFWfzl2ccRLj0bbSKNhFEUR0e7fZuWkwFJvneCcAEVCnlrtnNQk7EawaEFcFFD/mQNfU4Cq6eO5vCi\n
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=233ug6pl2hz5Qx0iLQjtP7cskjda9453w9q3PeLo4dAH7LT/RpdTYX68g/4/jdM6jEhIFqzuxTzKcNBmpNfOIgG7peVVnt8WfU06uqMDNZeQgi56awwhv8btRZN4J8b0dcKK36ozVZissrgsJd87SOiSqluDpxJ7gdX7gSinh7P6eYVp4TdFWfzl2ccRLj0bbSKNhFEUR0e7fZuWkwFJvneCcAEVCnlrtnNQk7EawaEFcFFD/mQNfU4Cq6eO5vCi\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting confirm prompt for callback /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: completed confirm prompt for callback :1.5@/org/gnome/keyring/Prompt/p8
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=I5vgW6S2rwRRFsyYj6xl4OGLJ+vwi5NdSE6pNOR9BRAWE4BpiwcfiTHf9dKlSAn8TUZ8sYgQ9ipmMvGEBzI8VlZLae7hjslQVDT11PTGhUPFNEWycpYxTH09US0cOiJKx+Ks/3313pwWYXh1dFanPuXqLVk5lhvYT9TO0FBLXAJRWzSfu7QTnUg8hwbmxePtGqBDocjybr0UYWgn6Ca/0mEk8UnBdjW4M2uaXo0sVBuqUx94SxOHG6HUJplOyFXc\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=I5vgW6S2rwRRFsyYj6xl4OGLJ+vwi5NdSE6pNOR9BRAWE4BpiwcfiTHf9dKlSAn8TUZ8sYgQ9ipmMvGEBzI8VlZLae7hjslQVDT11PTGhUPFNEWycpYxTH09US0cOiJKx+Ks/3313pwWYXh1dFanPuXqLVk5lhvYT9TO0FBLXAJRWzSfu7QTnUg8hwbmxePtGqBDocjybr0UYWgn6Ca/0mEk8UnBdjW4M2uaXo0sVBuqUx94SxOHG6HUJplOyFXc\n
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p8@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p8@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 9 /gcr/system-prompt/confirm-async
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.12
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: creating new GcrMockPrompt prompt
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.12: /org/gnome/keyring/Prompt/p9
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=sNC3MDr7IW8cXRRjp9eVJtAu4DHttHy0Irtv+GiWceibqKtRk0BYmxiHBVgfoVxYm4gpxaqVH8lJw+0DlJItf1R0J8JftONp8eXtLIwvAtAYo7eG4mUwmFBmvMkI5lJk/Izm9r9zQ0H1A3AWG+5zmrOIlOO0t0Cd34SKk6ZeEBakQz6SThJVF5PvqMb+fh0kPk9V0N8DKtNhsk/ZKemMhoVboObH1q5Y6M9QbwUGdJxxlUX68n5fGk6C1ip6NOP+\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=sNC3MDr7IW8cXRRjp9eVJtAu4DHttHy0Irtv+GiWceibqKtRk0BYmxiHBVgfoVxYm4gpxaqVH8lJw+0DlJItf1R0J8JftONp8eXtLIwvAtAYo7eG4mUwmFBmvMkI5lJk/Izm9r9zQ0H1A3AWG+5zmrOIlOO0t0Cd34SKk6ZeEBakQz6SThJVF5PvqMb+fh0kPk9V0N8DKtNhsk/ZKemMhoVboObH1q5Y6M9QbwUGdJxxlUX68n5fGk6C1ip6NOP+\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=nBpNNkK1an8XreD0hrEr7LugK2GiBQNdbrxfcTejPpotymp8ySGrrIozmpmUUHskibjms4QlfitBiFjE5Pi9JKr0iwrbpZg43iXmOUbmGUipxEYc9ynDvhIun0NV/QuwPiW7EtX1HUj8X3ohyL4+M98Ny9na16t9DkZ/ZmHadQjleDgETpdGZiaXTOMb/RibVnGFb6sgLsv1ssF80XWuvuBQCrVpgUOASBeZlHz+8Df5gNrHtx/7kqTUY43w4j/x\n
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=nBpNNkK1an8XreD0hrEr7LugK2GiBQNdbrxfcTejPpotymp8ySGrrIozmpmUUHskibjms4QlfitBiFjE5Pi9JKr0iwrbpZg43iXmOUbmGUipxEYc9ynDvhIun0NV/QuwPiW7EtX1HUj8X3ohyL4+M98Ny9na16t9DkZ/ZmHadQjleDgETpdGZiaXTOMb/RibVnGFb6sgLsv1ssF80XWuvuBQCrVpgUOASBeZlHz+8Df5gNrHtx/7kqTUY43w4j/x\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting confirm prompt for callback /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: completed confirm prompt for callback :1.5@/org/gnome/keyring/Prompt/p9
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=sNC3MDr7IW8cXRRjp9eVJtAu4DHttHy0Irtv+GiWceibqKtRk0BYmxiHBVgfoVxYm4gpxaqVH8lJw+0DlJItf1R0J8JftONp8eXtLIwvAtAYo7eG4mUwmFBmvMkI5lJk/Izm9r9zQ0H1A3AWG+5zmrOIlOO0t0Cd34SKk6ZeEBakQz6SThJVF5PvqMb+fh0kPk9V0N8DKtNhsk/ZKemMhoVboObH1q5Y6M9QbwUGdJxxlUX68n5fGk6C1ip6NOP+\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=sNC3MDr7IW8cXRRjp9eVJtAu4DHttHy0Irtv+GiWceibqKtRk0BYmxiHBVgfoVxYm4gpxaqVH8lJw+0DlJItf1R0J8JftONp8eXtLIwvAtAYo7eG4mUwmFBmvMkI5lJk/Izm9r9zQ0H1A3AWG+5zmrOIlOO0t0Cd34SKk6ZeEBakQz6SThJVF5PvqMb+fh0kPk9V0N8DKtNhsk/ZKemMhoVboObH1q5Y6M9QbwUGdJxxlUX68n5fGk6C1ip6NOP+\n
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p9@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p9@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 10 /gcr/system-prompt/confirm-cancel
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.13
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: creating new GcrMockPrompt prompt
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.13: /org/gnome/keyring/Prompt/p10
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=ximu/WTUTwgxFnaeRHVO+xz2ypwkiImhM85qFjTcl5n2V/qusQ3wwxo3h7vFYwo/hzncYK3WYBgh7eX6FtYB/tgbwT8VmEO9eGt9lZ9En/I7ZmSzvyzrpG1sGSoX97BjPvA24uJD8wcxi9M8dj2VYFW9kwKcbt1pDGuQBByrWM8osx2gz6A38sCZCIJZnSB9qphsuBfENUFBysc99spSuONGFtxq+r5+Z7h7SoiQ7HWbbmkzQxLcARUzEkenxC/s\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=ximu/WTUTwgxFnaeRHVO+xz2ypwkiImhM85qFjTcl5n2V/qusQ3wwxo3h7vFYwo/hzncYK3WYBgh7eX6FtYB/tgbwT8VmEO9eGt9lZ9En/I7ZmSzvyzrpG1sGSoX97BjPvA24uJD8wcxi9M8dj2VYFW9kwKcbt1pDGuQBByrWM8osx2gz6A38sCZCIJZnSB9qphsuBfENUFBysc99spSuONGFtxq+r5+Z7h7SoiQ7HWbbmkzQxLcARUzEkenxC/s\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=7xxT7/8HYzhnzKg7JGTiIfnF+kMGSbs3UEhnLTXH2Qalg+QoXMMvic5zft7CjeoTXEbHsLl32TLlwad8PTUal7cRO+Y9dXhxpaQxYaspq1CC3ZOkl4pYe+8SE7fW9NnPdSiuzVEG1OuRt2HtjUmnqW2Ar7Q0mZ3kM9Bhx06POryMXSBtzvT4bG/Bprrh8AS7jjgy6yg6bT1diUvtBAOAsVhvVf4RYtWcUTuJr8PGlOUe8Zc2fiIK13VeXXijMKjv\n
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=7xxT7/8HYzhnzKg7JGTiIfnF+kMGSbs3UEhnLTXH2Qalg+QoXMMvic5zft7CjeoTXEbHsLl32TLlwad8PTUal7cRO+Y9dXhxpaQxYaspq1CC3ZOkl4pYe+8SE7fW9NnPdSiuzVEG1OuRt2HtjUmnqW2Ar7Q0mZ3kM9Bhx06POryMXSBtzvT4bG/Bprrh8AS7jjgy6yg6bT1diUvtBAOAsVhvVf4RYtWcUTuJr8PGlOUe8Zc2fiIK13VeXXijMKjv\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting confirm prompt for callback /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: completed confirm prompt for callback :1.5@/org/gnome/keyring/Prompt/p10
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=ximu/WTUTwgxFnaeRHVO+xz2ypwkiImhM85qFjTcl5n2V/qusQ3wwxo3h7vFYwo/hzncYK3WYBgh7eX6FtYB/tgbwT8VmEO9eGt9lZ9En/I7ZmSzvyzrpG1sGSoX97BjPvA24uJD8wcxi9M8dj2VYFW9kwKcbt1pDGuQBByrWM8osx2gz6A38sCZCIJZnSB9qphsuBfENUFBysc99spSuONGFtxq+r5+Z7h7SoiQ7HWbbmkzQxLcARUzEkenxC/s\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=ximu/WTUTwgxFnaeRHVO+xz2ypwkiImhM85qFjTcl5n2V/qusQ3wwxo3h7vFYwo/hzncYK3WYBgh7eX6FtYB/tgbwT8VmEO9eGt9lZ9En/I7ZmSzvyzrpG1sGSoX97BjPvA24uJD8wcxi9M8dj2VYFW9kwKcbt1pDGuQBByrWM8osx2gz6A38sCZCIJZnSB9qphsuBfENUFBysc99spSuONGFtxq+r5+Z7h7SoiQ7HWbbmkzQxLcARUzEkenxC/s\n
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p10@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p10@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 11 /gcr/system-prompt/properties
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.14
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: creating new GcrMockPrompt prompt
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.14: /org/gnome/keyring/Prompt/p11
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=02wVVnjnBzTgNyJRi3DmI/RvtVWiW/zNHJnKBTAGawNMp0bXoijBKklOOUV0spKJRR5Qwy/AEEL8QrkCfCQPcUe+GKozG4xEJ68hLiG4vycnv2Os9EWIMYL0vJmNZN2tzvjWrt5UPtytv+FsaGTrsWCvSIu32IZ1y7y0gsS4cyR1+10F3CwkKVSwppUHp3Z4iEcwWKXabLot08UzLVQtFl3Am3fHMySvpVJjhlDZdz4iEK7vKhdyoxuJO8T0SPiH\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=02wVVnjnBzTgNyJRi3DmI/RvtVWiW/zNHJnKBTAGawNMp0bXoijBKklOOUV0spKJRR5Qwy/AEEL8QrkCfCQPcUe+GKozG4xEJ68hLiG4vycnv2Os9EWIMYL0vJmNZN2tzvjWrt5UPtytv+FsaGTrsWCvSIu32IZ1y7y0gsS4cyR1+10F3CwkKVSwppUHp3Z4iEcwWKXabLot08UzLVQtFl3Am3fHMySvpVJjhlDZdz4iEK7vKhdyoxuJO8T0SPiH\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p11@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p11@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 12 /gcr/system-prompt/properties-unset
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.15
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.15: /org/gnome/keyring/Prompt/p12
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=GP+ZM96kFwwVKM2V1esmE2k9fJJrlD/TQcw6eApHQbhoWNCvOxBRRHpWmO2J8Ut6yJLbYBwqe6dC+QTtRXCY4I8w672AkhAyTyJjKwNywrrpxwAun8+7aOEqA4HMJvdBnCqvYxUVuucOyasguBz9+0d0EH8xOM9c6H9u+YV6Ei8G7t6tAvDbxZQqu7WUs0hPYDRcYGvjNO3D4Y0S4CGJ9LaeuiMmPWn91FWuGYnRKb/bSe2q52+VgOvOQ6x2q7Rm\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=GP+ZM96kFwwVKM2V1esmE2k9fJJrlD/TQcw6eApHQbhoWNCvOxBRRHpWmO2J8Ut6yJLbYBwqe6dC+QTtRXCY4I8w672AkhAyTyJjKwNywrrpxwAun8+7aOEqA4HMJvdBnCqvYxUVuucOyasguBz9+0d0EH8xOM9c6H9u+YV6Ei8G7t6tAvDbxZQqu7WUs0hPYDRcYGvjNO3D4Y0S4CGJ9LaeuiMmPWn91FWuGYnRKb/bSe2q52+VgOvOQ6x2q7Rm\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p12@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p12@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 13 /gcr/system-prompt/properties-reset
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.16
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: creating new GcrMockPrompt prompt
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.16: /org/gnome/keyring/Prompt/p13
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=Q4HbmtZydSovWGMhzyRryu4WVpNXTSv3IYjj7dNeKp+USl78k4cqWvFi2Ht0rXT9iq5g7wrOqfGCMM34TV1MISWm2V++tjYl6pKWf1ZGOb24oqNdirCY8udq3stScbfAgQfVa65e/OT7gfSJrxBVNEbfu8TntcwbBZKfwIiISdEljWxLZr5S/QJyvJB3kIuLLd4x3phEPJsF79bpXiZikTJfq4CVCNl/moOP02vLE0qgI7DwA7oqrpAC3FNPZ9um\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=Q4HbmtZydSovWGMhzyRryu4WVpNXTSv3IYjj7dNeKp+USl78k4cqWvFi2Ht0rXT9iq5g7wrOqfGCMM34TV1MISWm2V++tjYl6pKWf1ZGOb24oqNdirCY8udq3stScbfAgQfVa65e/OT7gfSJrxBVNEbfu8TntcwbBZKfwIiISdEljWxLZr5S/QJyvJB3kIuLLd4x3phEPJsF79bpXiZikTJfq4CVCNl/moOP02vLE0qgI7DwA7oqrpAC3FNPZ9um\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: opening prompt for prompter: :1.16
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p14@:1.5
# Gcr-DEBUG: registered prompt :1.16: /org/gnome/keyring/Prompt/p14
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=gxKHNQCWam/pU0oBKlFkOTDP1jpuAKafRfy6Bi9Odhl49ImmEcsr9ZWiFL289S8ykt2d08BJUX+pWUnyxeoEpbvSp/vSf8utuvy7Sg5z4vfr+kPzbxds31/S9RvrGsQPBW6DCTETA+zeV6fHBIXaGpV8wE5SEKQnMUFu/4AXvq0m23o3HnUDzaAaE8pTb+FnF55heFL1R19LvEFedPqZTeXyXYS8ag8L+mcskRkhTbiFa7fLzHQnLRpQg0zdmaxA\n
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p14@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p14@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p14@:1.5, and ignoring reply
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=gxKHNQCWam/pU0oBKlFkOTDP1jpuAKafRfy6Bi9Odhl49ImmEcsr9ZWiFL289S8ykt2d08BJUX+pWUnyxeoEpbvSp/vSf8utuvy7Sg5z4vfr+kPzbxds31/S9RvrGsQPBW6DCTETA+zeV6fHBIXaGpV8wE5SEKQnMUFu/4AXvq0m23o3HnUDzaAaE8pTb+FnF55heFL1R19LvEFedPqZTeXyXYS8ag8L+mcskRkhTbiFa7fLzHQnLRpQg0zdmaxA\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting confirm prompt for callback /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: completed confirm prompt for callback :1.5@/org/gnome/keyring/Prompt/p13
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=Q4HbmtZydSovWGMhzyRryu4WVpNXTSv3IYjj7dNeKp+USl78k4cqWvFi2Ht0rXT9iq5g7wrOqfGCMM34TV1MISWm2V++tjYl6pKWf1ZGOb24oqNdirCY8udq3stScbfAgQfVa65e/OT7gfSJrxBVNEbfu8TntcwbBZKfwIiISdEljWxLZr5S/QJyvJB3kIuLLd4x3phEPJsF79bpXiZikTJfq4CVCNl/moOP02vLE0qgI7DwA7oqrpAC3FNPZ9um\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=Q4HbmtZydSovWGMhzyRryu4WVpNXTSv3IYjj7dNeKp+USl78k4cqWvFi2Ht0rXT9iq5g7wrOqfGCMM34TV1MISWm2V++tjYl6pKWf1ZGOb24oqNdirCY8udq3stScbfAgQfVa65e/OT7gfSJrxBVNEbfu8TntcwbBZKfwIiISdEljWxLZr5S/QJyvJB3kIuLLd4x3phEPJsF79bpXiZikTJfq4CVCNl/moOP02vLE0qgI7DwA7oqrpAC3FNPZ9um\n
# Gcr-DEBUG: opening prompt for prompter: :1.16
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p15@:1.5
# Gcr-DEBUG: registered prompt :1.16: /org/gnome/keyring/Prompt/p15
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p15@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p15@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p15@:1.5, and ignoring reply
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p13@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p13@:1.5, and ignoring reply
# Gcr-DEBUG: opening prompt for prompter: :1.16
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: creating new GcrMockPrompt prompt
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.16: /org/gnome/keyring/Prompt/p16
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=IHpuR7EbPaybzWzau3ePmKJRhq304FgWjyYG5x81Kggx/ztpT4MMA4bSPazhbnnmhSCaeujkYE4O777gEzoOrINTw5Zp82k5gbAflo8H6B2i0WcCrT77tXEUmpZWnkPenb5achR6muq1ARQ+lJtIcuIsJ7x4ziQjQ3X17todq/TKQP9EJPbYJevLJk6op2G4frcWPYWV6BSLrFO4FDcZvmRVGdF9+diOTFoBdbOkiPXBaahDsCXY3zzCASeD1lUj\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=IHpuR7EbPaybzWzau3ePmKJRhq304FgWjyYG5x81Kggx/ztpT4MMA4bSPazhbnnmhSCaeujkYE4O777gEzoOrINTw5Zp82k5gbAflo8H6B2i0WcCrT77tXEUmpZWnkPenb5achR6muq1ARQ+lJtIcuIsJ7x4ziQjQ3X17todq/TKQP9EJPbYJevLJk6op2G4frcWPYWV6BSLrFO4FDcZvmRVGdF9+diOTFoBdbOkiPXBaahDsCXY3zzCASeD1lUj\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p16@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p16@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 14 /gcr/system-prompt/close
# slow test /gcr/system-prompt/close executed in 2.31 secs
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.17
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.17: /org/gnome/keyring/Prompt/p17
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=fbujGbOmxck+U9t74+AjdRSR7nHAQnWV/+/4yd5wu9uaaa6Br2Uu9kgAx5jJ0XYhNPvMOp8OJAxeGGX3RC3XR4RUK9qlTF8efqo2OPtY65NQqctjYc9S/CdG8WSLk4x/rM07sJaLbQ0lsk/rRdUwXJ9Rwg87PxFTyNaIo1QprzFRfIWoDdWlPC/B/eeppHADIAFHjXnKtpoYGvPwW8/NbIpB3dRrBMke8gU+X5c9gyYZLU3jtrOiukSU/TQcT8DW\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=fbujGbOmxck+U9t74+AjdRSR7nHAQnWV/+/4yd5wu9uaaa6Br2Uu9kgAx5jJ0XYhNPvMOp8OJAxeGGX3RC3XR4RUK9qlTF8efqo2OPtY65NQqctjYc9S/CdG8WSLk4x/rM07sJaLbQ0lsk/rRdUwXJ9Rwg87PxFTyNaIo1QprzFRfIWoDdWlPC/B/eeppHADIAFHjXnKtpoYGvPwW8/NbIpB3dRrBMke8gU+X5c9gyYZLU3jtrOiukSU/TQcT8DW\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=alV14L3kBtCZX/jpIsPkcSZ1SLYJm/PlnfPMlsXZ7RDyrzKQXiikxCc7tsZfns4RBxuHLqfz9N6nniQIJbf0mrCzldNsRipwj91DQtQAugRMtqnXqYXbLsACQtlcdg4GDAUqBUVXaGMNIJkarZ7gIfEbzIqFpao0HWJ/lDZI4cfSfXiSHuHkx5fc0wvJ3GRR7oBZbRHNFqOerC45xW4dSLIS4DBAzZlRnoPvgrWapBf+8HsvGKa6ERzua9aqsZlU\n
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=alV14L3kBtCZX/jpIsPkcSZ1SLYJm/PlnfPMlsXZ7RDyrzKQXiikxCc7tsZfns4RBxuHLqfz9N6nniQIJbf0mrCzldNsRipwj91DQtQAugRMtqnXqYXbLsACQtlcdg4GDAUqBUVXaGMNIJkarZ7gIfEbzIqFpao0HWJ/lDZI4cfSfXiSHuHkx5fc0wvJ3GRR7oBZbRHNFqOerC45xW4dSLIS4DBAzZlRnoPvgrWapBf+8HsvGKa6ERzua9aqsZlU\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting password prompt for callback /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: cancelling active prompting operation for /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p17@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p17@:1.5, and ignoring reply
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: unregistering prompter
ok 15 /gcr/system-prompt/close-cancels
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.18
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.18: /org/gnome/keyring/Prompt/p18
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=G5cmZeAaCZZGk4Czrlcp2VlZYP7qhF5ggI/hbvxSN/wpZwym0HWn+PmrnzaO/HzMmwgxA0ArkPYpfOVTQLAVlXxzkeGw7Cx/jcHI3bhFe3TFa5Hc9txf0OhFemrDSK/zoZDRrCJkN8ihWJmZxfjfivlpiCx8y7kjFOyvcJjW3kuaU8nwocuNjNMlWiJSTM4hGf4JXssmUu2SSa8KTzjduYYKxqbdTDfy1/fVU0iBc8Fh52nl5vOTgW1tWYWJvG5b\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=G5cmZeAaCZZGk4Czrlcp2VlZYP7qhF5ggI/hbvxSN/wpZwym0HWn+PmrnzaO/HzMmwgxA0ArkPYpfOVTQLAVlXxzkeGw7Cx/jcHI3bhFe3TFa5Hc9txf0OhFemrDSK/zoZDRrCJkN8ihWJmZxfjfivlpiCx8y7kjFOyvcJjW3kuaU8nwocuNjNMlWiJSTM4hGf4JXssmUu2SSa8KTzjduYYKxqbdTDfy1/fVU0iBc8Fh52nl5vOTgW1tWYWJvG5b\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=6CkT62uG93mB6r/ER6i7msKjD62UpTfTJL0fcNbskvBglarbpw5s225GBFKPlD7s/f+JQ5vy20no9ttoLhGSdMYgGziAlWahh7aTeEFDjBFlqohwkFMAHIo0P4fAPybhh+VRtfs7F4qUz8ar+loYrx1+ImQ+MbrJjDFwxJeejHbd9yJmQjprzxP9eKzs9OyiEz4dj5WzS2Oxdh/3HEZYoUUId+/GUyRZB+mMH7HCRiJOL4FRHMFUOZYPd4EYnInI\n
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=6CkT62uG93mB6r/ER6i7msKjD62UpTfTJL0fcNbskvBglarbpw5s225GBFKPlD7s/f+JQ5vy20no9ttoLhGSdMYgGziAlWahh7aTeEFDjBFlqohwkFMAHIo0P4fAPybhh+VRtfs7F4qUz8ar+loYrx1+ImQ+MbrJjDFwxJeejHbd9yJmQjprzxP9eKzs9OyiEz4dj5WzS2Oxdh/3HEZYoUUId+/GUyRZB+mMH7HCRiJOL4FRHMFUOZYPd4EYnInI\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting confirm prompt for callback /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: completed confirm prompt for callback :1.5@/org/gnome/keyring/Prompt/p18
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=G5cmZeAaCZZGk4Czrlcp2VlZYP7qhF5ggI/hbvxSN/wpZwym0HWn+PmrnzaO/HzMmwgxA0ArkPYpfOVTQLAVlXxzkeGw7Cx/jcHI3bhFe3TFa5Hc9txf0OhFemrDSK/zoZDRrCJkN8ihWJmZxfjfivlpiCx8y7kjFOyvcJjW3kuaU8nwocuNjNMlWiJSTM4hGf4JXssmUu2SSa8KTzjduYYKxqbdTDfy1/fVU0iBc8Fh52nl5vOTgW1tWYWJvG5b\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=G5cmZeAaCZZGk4Czrlcp2VlZYP7qhF5ggI/hbvxSN/wpZwym0HWn+PmrnzaO/HzMmwgxA0ArkPYpfOVTQLAVlXxzkeGw7Cx/jcHI3bhFe3TFa5Hc9txf0OhFemrDSK/zoZDRrCJkN8ihWJmZxfjfivlpiCx8y7kjFOyvcJjW3kuaU8nwocuNjNMlWiJSTM4hGf4JXssmUu2SSa8KTzjduYYKxqbdTDfy1/fVU0iBc8Fh52nl5vOTgW1tWYWJvG5b\n
# Gcr-DEBUG: Calling the prompter StopPrompting method
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p18@:1.5, and waiting for reply
# Gcr-DEBUG: returned from PromptDone on /org/gnome/keyring/Prompt/p18@:1.5
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 16 /gcr/system-prompt/after-close-dismisses
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.19
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: creating new GcrMockPrompt prompt
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.19: /org/gnome/keyring/Prompt/p19
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=bWvzOeTlaFEE65z+13dDhX3Jp/aCo4zqib5I0S3u2ypEnyc5IY8/hv/4pf77iEZaMb6fIa00OJOu/Dod9GYRxlo5C2TkXbKOI0YGDLFaEKPkgrfDnN9ngiASED+Ay1MUk3O+PVGam4TfforX358DemWIKe2v1VqO9AWsgcwX6SkN5p0y+EkXFvXYiAGF+0VRyp+Rah5KEVLdukmGh+lGJM8uHfvDj7dh1LFXMwbkCGOyd2eTiU6o8cvBCdPFdODp\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=bWvzOeTlaFEE65z+13dDhX3Jp/aCo4zqib5I0S3u2ypEnyc5IY8/hv/4pf77iEZaMb6fIa00OJOu/Dod9GYRxlo5C2TkXbKOI0YGDLFaEKPkgrfDnN9ngiASED+Ay1MUk3O+PVGam4TfforX358DemWIKe2v1VqO9AWsgcwX6SkN5p0y+EkXFvXYiAGF+0VRyp+Rah5KEVLdukmGh+lGJM8uHfvDj7dh1LFXMwbkCGOyd2eTiU6o8cvBCdPFdODp\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=+5UOJGBInTKCrrUWKegpWlXdLOtjfMO4SrYJiTTIdS5koHsa+LAyDvGzP+z6921So8/UXJv+sJUMadvZgUU5gfNt6BElnZgpIMD7ciN4pIeW9Hn2rJ1qigJGRvBR1N6OP+IpAdxyyxXJ5xT7RafCq4TOsk4r72jBrh1O8BXTFnKLONZo+5EYSLtEiEMs/BIokQa34amFC3l7GlxH++k1mdIrzaaG3SmII7MOABIqdbIZL376t+61P/3NLVqZpzZt\n
# Gcr-DEBUG: failed to stop prompting: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=+5UOJGBInTKCrrUWKegpWlXdLOtjfMO4SrYJiTTIdS5koHsa+LAyDvGzP+z6921So8/UXJv+sJUMadvZgUU5gfNt6BElnZgpIMD7ciN4pIeW9Hn2rJ1qigJGRvBR1N6OP+IpAdxyyxXJ5xT7RafCq4TOsk4r72jBrh1O8BXTFnKLONZo+5EYSLtEiEMs/BIokQa34amFC3l7GlxH++k1mdIrzaaG3SmII7MOABIqdbIZL376t+61P/3NLVqZpzZt\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting confirm prompt for callback /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: completed confirm prompt for callback :1.5@/org/gnome/keyring/Prompt/p19
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=bWvzOeTlaFEE65z+13dDhX3Jp/aCo4zqib5I0S3u2ypEnyc5IY8/hv/4pf77iEZaMb6fIa00OJOu/Dod9GYRxlo5C2TkXbKOI0YGDLFaEKPkgrfDnN9ngiASED+Ay1MUk3O+PVGam4TfforX358DemWIKe2v1VqO9AWsgcwX6SkN5p0y+EkXFvXYiAGF+0VRyp+Rah5KEVLdukmGh+lGJM8uHfvDj7dh1LFXMwbkCGOyd2eTiU6o8cvBCdPFdODp\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: cancelling active prompting operation for /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: calling the PromptDone method on /org/gnome/keyring/Prompt/p19@:1.5, and ignoring reply
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p19@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=bWvzOeTlaFEE65z+13dDhX3Jp/aCo4zqib5I0S3u2ypEnyc5IY8/hv/4pf77iEZaMb6fIa00OJOu/Dod9GYRxlo5C2TkXbKOI0YGDLFaEKPkgrfDnN9ngiASED+Ay1MUk3O+PVGam4TfforX358DemWIKe2v1VqO9AWsgcwX6SkN5p0y+EkXFvXYiAGF+0VRyp+Rah5KEVLdukmGh+lGJM8uHfvDj7dh1LFXMwbkCGOyd2eTiU6o8cvBCdPFdODp\n
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: unregistering prompter
# Gcr-DEBUG: disposing prompter
# Gcr-DEBUG: finalizing prompter
ok 17 /gcr/system-prompt/close-from-prompter
# Gcr-DEBUG: registering prompter
# Gcr-DEBUG: opening prompt for prompter: :1.20
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: preparing a prompt for callback /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: registered prompt :1.20: /org/gnome/keyring/Prompt/p20
# Gcr-DEBUG: beginning the secret exchange: [sx-aes-1]\npublic=y8BgmK0X1I47dAaYi7RdGOGWCALV8vRe4s6/CHF0qTeC5z2CNGgcdDELMLxO0p1vQsYj1/BJfZ2nbPFckmdmHdhh554ovdQxe20SCzvDy2vJsX/ujiPN9pz3mXOZgZj8Y4PIK1YvQkCMgpjOY3A9XIbP6CL0IC8FeQazHtJZX7UO70Jr1sYXmcFWpecQHRLOe9X8+RWLathjePmYk7qsNywBC7yRp+pM2sDzwAo8bP7UvNMNB/KQx3XC4I5axIoA\n
# Gcr-DEBUG: calling the PromptReady method on /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: creating new secret exchange
# Gcr-DEBUG: automatically selecting secret exchange protocol
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=y8BgmK0X1I47dAaYi7RdGOGWCALV8vRe4s6/CHF0qTeC5z2CNGgcdDELMLxO0p1vQsYj1/BJfZ2nbPFckmdmHdhh554ovdQxe20SCzvDy2vJsX/ujiPN9pz3mXOZgZj8Y4PIK1YvQkCMgpjOY3A9XIbP6CL0IC8FeQazHtJZX7UO70Jr1sYXmcFWpecQHRLOe9X8+RWLathjePmYk7qsNywBC7yRp+pM2sDzwAo8bP7UvNMNB/KQx3XC4I5axIoA\n
# Gcr-DEBUG: generating public key
# Gcr-DEBUG: returned from the PromptReady method on /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: prompting for password
# Gcr-DEBUG: sending the secret exchange: [sx-aes-1]\npublic=4ZL9U43pf19mLbr3jWr3tTU5GJV9m+QOp4kiMw9OSmLh/sq/KD3v3uyAPEL6DlBKrzd4oiFDtudQOlE/BfjzB2IwjFIvQbcSuPDqKnUzSjK00YGlUt/f9VybGgKn3nBhU93ZduJ5W31IBODK8np5jbj4SfdDjay5wM6w2bXRahHJfDvb02GE8T1xi2X2gNCgpDdbDG0iz1K7ZDPrPvm9pbP6ofKQbJZGrISKkTrc+GBbEx2ik3S+oj3kfug6lXHZ\n
# Gcr-DEBUG: opening prompt for prompter: :1.20
# Gcr-DEBUG: connecting to bus
# Gcr-DEBUG: connected to bus
# Gcr-DEBUG: calling BeginPrompting method on prompter
# Gcr-DEBUG: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: receiving secret exchange: [sx-aes-1]\npublic=4ZL9U43pf19mLbr3jWr3tTU5GJV9m+QOp4kiMw9OSmLh/sq/KD3v3uyAPEL6DlBKrzd4oiFDtudQOlE/BfjzB2IwjFIvQbcSuPDqKnUzSjK00YGlUt/f9VybGgKn3nBhU93ZduJ5W31IBODK8np5jbj4SfdDjay5wM6w2bXRahHJfDvb02GE8T1xi2X2gNCgpDdbDG0iz1K7ZDPrPvm9pbP6ofKQbJZGrISKkTrc+GBbEx2ik3S+oj3kfug6lXHZ\n
# Gcr-DEBUG: deriving shared transport key
# Gcr-DEBUG: deriving transport key
# Gcr-DEBUG: starting password prompt for callback /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p21@:1.5
# Gcr-DEBUG: registered prompt :1.20: /org/gnome/keyring/Prompt/p21
# Gcr-DEBUG: caller vanished for callback /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: cancelling active prompting operation for /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: closing the prompt
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p20@:1.5
# Gcr-DEBUG: caller vanished for callback /org/gnome/keyring/Prompt/p21@:1.5
# Gcr-DEBUG: stopping prompting for operation /org/gnome/keyring/Prompt/p21@:1.5
# Gcr-DEBUG: prompter name owner has vanished: :1.20
# Gcr-DEBUG: prompter name owner has vanished: :1.20
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: closing prompt
# Gcr-DEBUG: unregistering prompter
ok 18 /gcr/system-prompt/watch-cancels
# slow test /gcr/system-prompt/watch-cancels executed in 1.01 secs
# End of system-prompt tests
# End of gcr tests
==============================================================================


Summary of Failures:

17/40 gcr:gck / object             FAIL            0.03s   killed by signal 11 SIGSEGV

Ok:                 39
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            0
Timeout:            0
dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 meson test returned exit code 1
make[1]: *** [debian/rules:30: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:18: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: 1057562@bugs.debian.org

Subject: Re: gcr4: FTBFS: failing tests

Date: Sun, 21 Jan 2024 10:26:19 -0500

Control: severity -1 important

I believe the gcr tests are just flaky.

Thank you,
Jeremy Bícha

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

From: Sebastian Ramacher <sebastian@ramacher.at>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org

Subject: Re: Bug#1057562: gcr4: FTBFS: failing tests

Date: Fri, 9 Feb 2024 20:56:11 +0100

Control: tags -1 serious

Hi

On 2024-01-21 10:26:19 -0500, Jeremy Bícha wrote:
> Control: severity -1 important
> 
> I believe the gcr tests are just flaky.

They are now also failing on the buildds:
https://buildd.debian.org/status/fetch.php?pkg=gcr4&arch=amd64&ver=4.1.0-2%2Bb1&stamp=1707501299&raw=0

If they are flaky, please disable them or - if possible - make them
non-flaky.

Cheers
-- 
Sebastian Ramacher

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

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

To: 1057562-close@bugs.debian.org

Subject: Bug#1057562: fixed in gcr4 4.2.0-2

Date: Tue, 27 Feb 2024 19:19:21 +0000

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

Source: gcr4
Source-Version: 4.2.0-2
Done: Jeremy Bícha <jbicha@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
gcr4, 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 1057562@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha <jbicha@ubuntu.com> (supplier of updated gcr4 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: SHA512

Format: 1.8
Date: Tue, 27 Feb 2024 14:02:40 -0500
Source: gcr4
Built-For-Profiles: noudeb
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Jeremy Bícha <jbicha@ubuntu.com>
Closes: 1057562
Changes:
 gcr4 (4.2.0-2) unstable; urgency=medium
 .
   * Ignore build test failures on s390x (Closes: #1057562)
Checksums-Sha1:
 ed8bbdcedd6ba9d169e3ce375de0eca198f43e1e 3066 gcr4_4.2.0-2.dsc
 4a37e33763b8538ca6bf046b82df6eeaac3b2294 21564 gcr4_4.2.0-2.debian.tar.xz
 aeebc61f6ca22fd8618f5288d70b370b16475e1b 20183 gcr4_4.2.0-2_source.buildinfo
Checksums-Sha256:
 e5042bc463577ea6f61d191125ddd7fc199fa56186171abdf89a03723bae0a6e 3066 gcr4_4.2.0-2.dsc
 291b7d6f8c13a73ca8ba5203cc7c2553b676b350c3ddde11a024afd7788fbc11 21564 gcr4_4.2.0-2.debian.tar.xz
 7b7a576d05cd664ade3baf9dcd5e30c53f93175f9b21dfe61770e09cd92c3003 20183 gcr4_4.2.0-2_source.buildinfo
Files:
 bc4e78d4f53fd3b7fe5dbface8333f17 3066 gnome optional gcr4_4.2.0-2.dsc
 5f341c5338ebba0969beb66b3ec48e79 21564 gnome optional gcr4_4.2.0-2.debian.tar.xz
 6c0a2b1465719f338cd45f0e8192d4d3 20183 gnome optional gcr4_4.2.0-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXeMfcACgkQ5mx3Wuv+
bH3yRg//fX+pYujVv2pxl75LGUXmrJfHsCSB7AygvX5PiMdwVntuwqEcOE7G66vz
z7PLly4gtlER2YUJzkJ+EjXpBk+4jQEV4s/wW38kX39rINA/qs+oIcNIMb+QdKaL
uQRMDoQRHu54AMDGEPrZUdNEVdHaQANC0Kasw7TJGKZOPMbXSCRZhSkyL8mxkZp5
C+0r4RxlNK1GZOFEsPc1j8fN3JehT/FvF3+9zPxvtB2FPWEQwmQ3dCNzM/DGA8tB
q/EJcggN6gJQSBYLAGN+GAdJ2Fpf5juo89nAdkt+OZ+gkjjfIYJDbeNLEjJRw9UV
lRg4Lzp9/gc8s+NquLT/PQe3fzACYM1//b43CXNKq3U99lOPSZZrEEQPVuvg9FOd
nRDPSs08kCxYm6M1xEVLhSwcMLvOFVa6eNFjWX8hIVyn28KWt5nrDqcVEyNXQFKL
4zxIiMUlFNZtTeCEFvQv2ayrByNB91RK+2TVsjLvTMwi41ZC7vJCNH4pi1iAI99N
6XQ4MqaeYdaauCDWeWKDOrPV//aaStWkUGNgTNhSR8J1Ai/vbPe7HZNCvq3GD3H/
FM/SVEXhlq4LdhJe6VXnMWNNjYkTqJGWg8AnOiSC70hH1zp5DT51GWEr86ClAYwV
mFdhZmoIQxzUVnoOfD5Z756XMroZDNG7oGVd7gULopXsmjMJHZQ=
=txt3
-----END PGP SIGNATURE-----

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

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

From: Santiago Vila <sanvila@debian.org>

To: 1057562@bugs.debian.org

Subject: Re: Bug#1057562 closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Jeremy Bícha <jbicha@ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

Date: Fri, 1 Mar 2024 12:33:03 +0100

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

reopen 1057562
found 1057562 4.2.0-3
thanks

> Ignore build test failures on s390x (Closes: #1057562)

This is wrong for several reasons.

- The bug report did not say anything about s390x.

- This is still happening on version 4.2.0-3. I can still reproduce
  it 100% of the time here, and I'm using amd64. Build log attached.

- I included a paragraph saying this which has been completely ignored:

> If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

- Even if you don't care about the end user being able to build
the package from source and your only concern is flakiness on the
official buildds (which is not a good way to "fix" the problem, btw),
this is still flaky on the official buildds:

https://buildd.debian.org/status/fetch.php?pkg=gcr4&arch=amd64&ver=4.2.0-3&stamp=1709067945&raw=0


My offer for a machine where this happens 100% of the time still holds
if you need it.

Thanks.

[gcr4_4.2.0-3_amd64-20240301T110721.878Z.gz (application/gzip, attachment)]

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Santiago Vila <sanvila@debian.org>, 1057562@bugs.debian.org

Subject: Re: Bug#1057562: closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Jeremy Bícha <jbicha@ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

Date: Sun, 3 Mar 2024 11:38:40 -0500

Control: severity -1 important
Control: affects -1 src:gcr

On Fri, Mar 1, 2024 at 6:36 AM Santiago Vila <sanvila@debian.org> wrote:
> > Ignore build test failures on s390x (Closes: #1057562)
>
> This is wrong for several reasons.
>
> - The bug report did not say anything about s390x.

s390x is the only architecture where the flakiness of the gcr:gck /
object build test is severe enough to unreasonably interfere with
timely building of gcr & gcr4.

Debian is full of packages where the build tests and autopkgtests are
flaky enough to be disruptive to someone expecting 100% pass rates.
There is currently no one on the Debian GNOME team with the time to
investigate and properly fix these issues.

The occasional failure is enough to remind us of this issue. I don't
think it's helpful to just disable the test since it may disguise a
real problem that someone can work on once they get sufficiently
annoyed by the issue. Also, it may be important to recognize if the
failure rate for this test on official buildds increases
significantly. The failure rate did increase on s390x but we don't
really treat s390x as a supported Desktop architecture and don't have
capacity to spend much time dealing with s390x.

I am demoting this bug because it is a valid bug, but also not severe
enough to get gcr excluded from Debian Testing.

Thank you,
Jeremy Bícha

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

From: Santiago Vila <sanvila@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org, Sebastian Ramacher <sebastian@ramacher.at>

Subject: Re: Bug#1057562: closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Jeremy Bícha <jbicha@ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

Date: Tue, 12 Mar 2024 20:32:26 +0100

El 3/3/24 a las 17:38, Jeremy Bícha escribió:
> Control: severity -1 important
> Control: affects -1 src:gcr
> 
> On Fri, Mar 1, 2024 at 6:36 AM Santiago Vila <sanvila@debian.org> wrote:
>>> Ignore build test failures on s390x (Closes: #1057562)
>>
>> This is wrong for several reasons.
>>
>> - The bug report did not say anything about s390x.
> 
> s390x is the only architecture where the flakiness of the gcr:gck /
> object build test is severe enough to unreasonably interfere with
> timely building of gcr & gcr4.

You keep misrepresenting the bug I reported.

The bug report was not about a flaky test in a generic sense.

And it was not about the effect of such flaky test in the official buildds either.

What the bug report said is that whenever I try to build the package
on several virtual machines from AWS of different types, the build fails.

ALWAYS.

So, this is not about an occasional failure. This is about a permanent failure.

Here is my build history:

Status: failed      gcr4_4.1.0-2_amd64-20230322T215308.971Z
Status: failed      gcr4_4.1.0-2_amd64-20230322T215447.211Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202053.367Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202058.856Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202121.876Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202342.316Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202518.944Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202604.013Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202834.489Z
Status: failed      gcr4_4.1.0-2_amd64-20230922T202921.776Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T214526.762Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T215238.884Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T215413.813Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T215359.115Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T215627.137Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T215937.574Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T221515.395Z
Status: failed      gcr4_4.1.0-2_amd64-20230930T221739.810Z
Status: failed      gcr4_4.1.0-2_amd64-20231130T041100.202Z
Status: failed      gcr4_4.1.0-2_amd64-20231205T160411.736Z
Status: failed      gcr4_4.1.0-2_amd64-20231213T155044.129Z
Status: failed      gcr4_4.1.0-2_amd64-20231213T160911.601Z
Status: failed      gcr4_4.1.0-2_amd64-20240129T170626.580Z
Status: failed      gcr4_4.1.0-2_amd64-20240129T170930.627Z
Status: failed      gcr4_4.1.0-2_amd64-20240129T171059.244Z
Status: failed      gcr4_4.1.0-2_amd64-20240129T171811.347Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110606.957Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110607.721Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110608.780Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110608.127Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110609.765Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110718.547Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110719.934Z
Status: failed      gcr4_4.2.0-3_amd64-20240301T110721.878Z

This is a violation of a *must* directive in Policy, because
Debian policy says this:

If build-time dependencies are specified, it must be possible to build the package and produce working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships).

> Debian is full of packages where the build tests and autopkgtests are
> flaky enough to be disruptive to someone expecting 100% pass rates.

This is a strawman. I'm *not* expecting a 100% pass rate.

A pass rate of 100% would correspond to a failure rate of 0%.

I do not expect a failure rate of 0%.

I just expect a failure rate which is *not* 100%.

> There is currently no one on the Debian GNOME team with the time to
> investigate and properly fix these issues.

In such case the failing test is completely useless and even harmful.

When we have unit tests, they are enabled with the aim of
"doing something" when they fail. If we do nothing when they
fail, we are wasting the time of everybody involved.

> The occasional failure is enough to remind us of this issue.

If this is really about "reminding", I can put a cron job to
email you a reminder weekly or monthly. Even a postit note in your
monitor would be better than this.

But not this.

> I don't
> think it's helpful to just disable the test since it may disguise a
> real problem that someone can work on once they get sufficiently
> annoyed by the issue.

Well, but this is *already* a real problem: The package does not
build in some systems. Not an occasional failure, but not at all.

> Also, it may be important to recognize if the
> failure rate for this test on official buildds increases
> significantly. The failure rate did increase on s390x but we don't
> really treat s390x as a supported Desktop architecture and don't have
> capacity to spend much time dealing with s390x.

And you keep mentioning s390x when the original bug report did not
mention s390x at all.

In fact, Sebastian Ramacher, I guess that acting as a Release Manager,
restored the serious severity in the past, and when he did he
included a link specifically to the flaky amd64 build, not to the
s390x build.

But you downgraded the bug again.

Please ensure that this package builds from source for everybody,
not only in the official buildds.

Debian is a free software distribution. The end user has the right to
rebuild the package, and to do so without having to jump through hoops.

Thanks.

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Santiago Vila <sanvila@debian.org>

Cc: 1057562@bugs.debian.org, Sebastian Ramacher <sebastian@ramacher.at>

Subject: Re: Bug#1057562: closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Jeremy Bícha <jbicha@ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

Date: Tue, 12 Mar 2024 15:48:24 -0400

On Tue, Mar 12, 2024 at 3:32 PM Santiago Vila <sanvila@debian.org> wrote:
> This is a violation of a *must* directive in Policy, because
> Debian policy says this:
>
> If build-time dependencies are specified, it must be possible to build the package and produce working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships).

I disagree with your interpretation of Debian Policy. It is clearly
possible to build gcr and gcr4 on a system with only essential and
build-essential installed. See
https://buildd.debian.org/status/package.php?p=gcr4

Debian Policy does not say that it is a severity: serious bug because
you are unable to compile gcr4 on your particular AWS instance. I
understand that this bug appears serious to you. I also agree that
there is a real bug in gcr. Perhaps the bug is a race condition.
Fixing the issue that causes gcr build tests to fail 100% in your test
case may also fix the flakiness issue seen on the official buildds.

One problem with your insistence on declaring this bug serious was
that it put epiphany-browser on the auto-removal list. It was not that
critical. (That issue is obsolete since key packages are now using
gcr4.)

Unfortunately, the Debian GNOME team is too small for the amount of
work to be done and the number of open bugs. This bug is not so severe
that it requires my immediate attention compared to everything else
nor is it easy enough that I can fix it in a few minutes. Instead of
complaining about the severity the maintainer has assigned to the bug,
I guess you could try fixing it?

Thank you,
Jeremy Bícha

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

From: Colin Watson <cjwatson@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org

Cc: Santiago Vila <sanvila@debian.org>, Sebastian Ramacher <sebastian@ramacher.at>

Subject: Re: Bug#1057562: closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Jeremy Bícha <jbicha@ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

Date: Tue, 23 Apr 2024 15:59:58 +0100

On Tue, Mar 12, 2024 at 03:48:24PM -0400, Jeremy Bícha wrote:
> Debian Policy does not say that it is a severity: serious bug because
> you are unable to compile gcr4 on your particular AWS instance. I
> understand that this bug appears serious to you. I also agree that
> there is a real bug in gcr. Perhaps the bug is a race condition.
> Fixing the issue that causes gcr build tests to fail 100% in your test
> case may also fix the flakiness issue seen on the official buildds.

I've been attempting to debug this on an AWS instance provided by
Santiago.  So far I'm afraid I can only report some partial progress,
but I might as well write down what I've got so far.

Whatever the bug is, it is highly sensitive to small perturbations.  For
instance, I found that commenting out non-failing g_test_add calls from
gck/test-gck-object.c:main (even those that run _after_ the tests that
typically fail) was enough to make it fail significantly less often.  I
suspect that this is just the effect of tweaking the state of hash
tables or a random number generator or something.

More unfortunately, attaching almost any kind of debugging tool seems to
perturb timing such that the problem is no longer reproducible; in
particular I was unable to reproduce failures under gdb.  The best I
could do was to generate a core dump, as follows:

  $ gdb gck/test-gck-object core
  GNU gdb (Debian 13.2-1+b1) 13.2
  Copyright (C) 2023 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  <https://www.gnu.org/software/gdb/bugs/>.
  Find the GDB manual and other documentation resources online at:
      <http://www.gnu.org/software/gdb/documentation/>.
  
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from gck/test-gck-object...
  [New LWP 31755]
  [New LWP 31753]
  [New LWP 31754]
  [New LWP 31751]
  [New LWP 31756]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/home/cjwatson/gcr4-4.2.0/obj-x86_64-linux-gnu/gck/test-gck-object'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x00007f4fef3a5633 in find_attribute (attr_type=3, n_attrs=12008468691120727718, attrs=0x55bef952d90a) at ../gck/gck-attributes.c:336
  336                     if (attrs[i].type == attr_type)
  [Current thread is 1 (Thread 0x7f4fed97a6c0 (LWP 31755))]
  (gdb) thread apply all bt
  
  Thread 5 (Thread 0x7f4fed1796c0 (LWP 31756)):
  #0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  #1  0x00007f4fef2ffc90 in g_cond_wait_until () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x00007f4fef26e143 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x00007f4fef2d24ba in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x00007f4fef2d1ab1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x00007f4fef08f45c in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
  #6  0x00007f4fef10fbbc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
  
  Thread 4 (Thread 0x7f4fee9c4a00 (LWP 31751)):
  #0  0x00007f4fef102abf in __GI___poll (fds=0x55bba2e90cb0, nfds=1, timeout=500) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x00007f4fef2a4277 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x00007f4fef2a4c1f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x000055bba2564664 in loop_wait_until (timeout=<optimized out>) at ../egg/egg-testing.c:310
  #4  0x000055bba2562a4d in test_find_objects (test=0x55bba2e8f5c0, unused=<optimized out>) at ../gck/test-gck-object.c:403
  #5  0x00007f4fef2cf71e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #6  0x00007f4fef2cf513 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x00007f4fef2cf513 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x00007f4fef2cfc32 in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x00007f4fef2cfcb8 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x000055bba2564b96 in egg_tests_run_with_loop () at ../egg/egg-testing.c:326
  #11 0x000055bba256268e in main (argc=<optimized out>, argv=<optimized out>) at ../gck/test-gck-object.c:426
  
  Thread 3 (Thread 0x7f4fee17b6c0 (LWP 31754)):
  #0  0x00007f4fef102abf in __GI___poll (fds=0x55bba2e904b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x00007f4fef2a4277 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x00007f4fef2a4930 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x00007f4fef2a4981 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x00007f4fef2d1ab1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x00007f4fef08f45c in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
  #6  0x00007f4fef10fbbc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
  
  Thread 2 (Thread 0x7f4fee97c6c0 (LWP 31753)):
  #0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  #1  0x00007f4fef2ffac4 in g_cond_wait () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x00007f4fef26e16b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x00007f4fef2d213a in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x00007f4fef2d1ab1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x00007f4fef08f45c in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
  #6  0x00007f4fef10fbbc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
  
  --Type <RET> for more, q to quit, c to continue without paging--
  Thread 1 (Thread 0x7f4fed97a6c0 (LWP 31755)):
  #0  0x00007f4fef3a5633 in find_attribute (attr_type=3, n_attrs=12008468691120727718, attrs=0x55bef952d90a) at ../gck/gck-attributes.c:336
  #1  gck_attributes_find (attrs=attrs@entry=0x55bba2e8a980, attr_type=3) at ../gck/gck-attributes.c:2077
  #2  0x00007f4fee9b616c in enumerate_and_find_objects (object=2, attrs=0x55bba2e8a980, user_data=0x7f4fed979ac0) at ../gck/gck-mock.c:1081
  #3  0x00007f4fee9b8237 in gck_mock_module_enumerate_objects (handle=handle@entry=113, func=func@entry=0x7f4fee9b6110 <enumerate_and_find_objects>, user_data=user_data@entry=0x7f4fed979ac0) at ../gck/gck-mock.c:203
  #4  0x00007f4fee9b8380 in gck_mock_C_FindObjectsInit (hSession=113, pTemplate=0x7f4fe4001770, ulCount=1) at ../gck/gck-mock.c:1114
  #5  0x00007f4fef3b13e9 in perform_find_objects (args=0x55bba2e95980) at ../gck/gck-session.c:1527
  #6  0x00007f4fef3b91d6 in perform_call (args=<optimized out>, cancellable=<optimized out>, cancellable@entry=0x55bba2e95980, func=<optimized out>) at ../gck/gck-call.c:67
  #7  perform_call_chain (perform=0x7f4fef3b1370 <perform_find_objects>, complete=0x0, cancellable=cancellable@entry=0x0, args=0x55bba2e95980) at ../gck/gck-call.c:97
  #8  0x00007f4fef3b936b in _gck_call_thread_func (task=0x55bba2e959b0, source_object=<optimized out>, task_data=0x55bba2e93250, cancellable=0x0) at ../gck/gck-call.c:132
  #9  0x00007f4feeed0ca7 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #10 0x00007f4fef2d2462 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x00007f4fef2d1ab1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x00007f4fef08f45c in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
  #13 0x00007f4fef10fbbc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

But the failures present unreliably in different ways (SIGSEGV, SIGTRAP,
etc.); this is just one of them.  My suspicion is that this is a
thread-safety issue of some kind, perhaps something like accesses to a
hash table not being locked properly, but that's just a guess.  I'm not
even sure whether it's in gcr4 or in some other layer of the stack.

I'd be happy to try some other things if anyone has pointers for where
might be good places to look, or things I might be able to tweak to make
the bug more reliably reproducible (e.g. places to insert artificial
delays).

I remain entirely unable to reproduce this bug in any form on my laptop.

-- 
Colin Watson (he/him)                              [cjwatson@debian.org]

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Colin Watson <cjwatson@debian.org>

Cc: 1057562@bugs.debian.org, Santiago Vila <sanvila@debian.org>, Sebastian Ramacher <sebastian@ramacher.at>

Subject: Re: Bug#1057562: closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Jeremy Bícha <jbicha@ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

Date: Tue, 23 Apr 2024 11:05:21 -0400

On Tue, Apr 23, 2024 at 11:00 AM Colin Watson <cjwatson@debian.org> wrote:
> I've been attempting to debug this on an AWS instance provided by
> Santiago.  So far I'm afraid I can only report some partial progress,
> but I might as well write down what I've got so far.

Colin, thanks for looking into this issue. It also affects source gcr
(which is just the older version of gcr4).

If you have time, feel free to forward this issue to
https://gitlab.gnome.org/GNOME/gcr/-/issues/

Jeremy Bícha

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

From: Andreas Tille <andreas@an3as.eu>

To: 1057562@bugs.debian.org

Subject: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Mon, 6 May 2024 21:34:02 +0200

Control: forwarded -1 https://gitlab.gnome.org/GNOME/gcr/-/issues/119
thanks

Hi,

this issue was reported upstream.  I would have pointed the issue to the
Debian BTS but for whatever reason my login is not accepted.  Santiago,
since you can provide VMs where the problem is reproducible which seems
to be a problem for the reporter of the issue, would you also offer such
a VM to gcr4 upstream?

If yes, it would be cool to add this info to their bug tracker.  In case
this might be a problem for you and nobody else has a valid login I try
to get a login tomorrow and will proxy this information.

Kind regards
   Andreas.

-- 
https://fam-tille.de

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

From: Santiago Vila <sanvila@debian.org>

To: Andreas Tille <andreas@an3as.eu>, 1057562@bugs.debian.org

Subject: Re: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Tue, 7 May 2024 01:42:32 +0200

> would you also offer such a VM to gcr4 upstream?

Yes.

(Or just tell them that it fails 100% of the time on AWS
instances of type m6a.large and r6a.large, which are the
ones I tried).

(btw: I tried registering myself to gnome's gitlab right now,
but did not receive confirmation email, hope they can help).

Thanks.

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

From: Santiago Vila <sanvila@debian.org>

To: Andreas Tille <andreas@an3as.eu>, 1057562@bugs.debian.org

Subject: Re: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Tue, 7 May 2024 13:49:28 +0200

Hi.

They finally enabled my account in gnome's gitlab and I have now offered them
hardware to reproduce it, if they need it.

Thanks.

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Santiago Vila <sanvila@debian.org>, 1057562@bugs.debian.org

Cc: Andreas Tille <andreas@an3as.eu>

Subject: Re: Bug#1057562: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Fri, 21 Mar 2025 14:08:54 -0400

Santiago,

I uploaded gcr 4 4.4.0.1-1 today with an upstream change that disabled
parallel running for some of the gck tests. Could you check if the
build failure bug appears to be fixed in this version? If so, I can
cherry-pick this change to the older src gcr too.

https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/165

Thank you,
Jeremy Bícha

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

From: Santiago Vila <sanvila@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org, Simon McVittie <smcv@debian.org>

Cc: Andreas Tille <andreas@an3as.eu>

Subject: Re: Bug#1057562: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Fri, 21 Mar 2025 20:27:20 +0100

El 21/3/25 a las 19:08, Jeremy Bícha escribió:
> I uploaded gcr 4 4.4.0.1-1 today with an upstream change that disabled
> parallel running for some of the gck tests. Could you check if the
> build failure bug appears to be fixed in this version? If so, I can
> cherry-pick this change to the older src gcr too.
> 
> https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/165

Not fixed according to preliminary tests. Still fails randomly at best.

I've had enough with this bug. Please ask any additional testing
to Simon McVittie (in Cc), as he's also a member of GNOME Team
and he will be able to reproduce this in a VM for which he still
has access. I can provide another VM for you if you need it
(please contact me privately for details).

A Release Manager (Sebastian Ramacher) specifically asked you
in this bug to *either* fix the test *or* disable it. Since we have
been unable to fix it, I would really hope that you really consider
to disable it this time, as flaky tests do more harm than good.

Thanks.

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

From: Santiago Vila <sanvila@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org

Cc: Andreas Tille <andreas@an3as.eu>

Subject: Re: Bug#1057562: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Fri, 21 Mar 2025 23:31:49 +0100

El 21/3/25 a las 19:08, Jeremy Bícha escribió:
> I uploaded gcr 4 4.4.0.1-1 today with an upstream change that disabled
> parallel running for some of the gck tests. Could you check if the
> build failure bug appears to be fixed in this version?

Ok, I've built the package 200 times in my setup.

On AWS machines of type m7a.medium and r7a.medium, the failure
rate is 100%, i.e. the build always fails. Incidentally, those
machines have 1 CPU, but I'm unable to tell if that's what triggers
the build failure or maybe the overall speed. In either case,
build-essential has never implied multi-core, so RC or not,
this is still a violation of Debian Policy.

On AWS machines of type r7a.large, m7a.large or c7a.large, the failure
rate is around 8%. Those machines have 2 CPUs. This is a lot better
than before, but still flaky.

I've put all the failed build logs I got here for you to see:

https://people.debian.org/~sanvila/build-logs/gcr4/

If the tests fail in some cases but they work in other cases, it means
that a test failure does not mean the program is wrong, i.e. the
tests are flaky, in which case it makes absolutely no sense to
punish QA testers with build failures that "have to be ignored".

The right way to ignore a test failure is by disabling it
to begin with.

Please disable the flaky tests, they do more harm than good.

Thanks.

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

From: Santiago Vila <sanvila@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org

Cc: Andreas Tille <andreas@an3as.eu>

Subject: Re: Bug#1057562: Forwarded upstream (Was: gcr4: FTBFS: failing tests)

Date: Fri, 21 Mar 2025 23:48:02 +0100

El 21/3/25 a las 23:31, Santiago Vila escribió:
> I've put all the failed build logs I got here for you to see:
> 
> https://people.debian.org/~sanvila/build-logs/gcr4/

To save anybody the trouble of looking at the above, here is a summary:

In all cases, the test which fails is always the same:

18/43 gcr:gck / object             FAIL

This should be easy to disable. This is not as if we had the package
without any tests at all. It's just one test which may not be trusted.

Thanks.

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Santiago Vila <sanvila@debian.org>

Cc: Debian Release Team <debian-release@lists.debian.org>, 1057562@bugs.debian.org

Subject: Re: Some severities to reconsider due to flaky tests

Date: Wed, 9 Apr 2025 08:26:38 -0400

On Wed, Apr 9, 2025 at 7:02 AM Santiago Vila <sanvila@debian.org> wrote:
> Dear Release Managers:
>
> Based on this reply by Paul:
>
> https://lists.debian.org/debian-devel/2025/04/msg00065.html
>
> I'd like to request that the severity of the following bugs is raised
> to serious again:
 > ..
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562
>
> (Raised by Sebastian to serious, downgraded later by the maintainer)
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069402
>
> This is essentially the same as #1057562, except that it's
> for gcr version 3 which is in a different package.
>
> Note that both gcr and gcr4 are key packages, so a serious severity
> will not make the package to be removed.

It feels like there is less reason to argue about severity for gcr & gcr4 then?

> A brief explanation for the maintainers that we don't want
> flaky tests in trixie would also be nice.

"flaky" is vague and until there is a specific standard for failure
rate, this is going to be subject to maintainer discretion to some
degree.

As of 4.4.0.1, gcr4 does not appear to be flaky at all in the official
buildds or on the reproducible builds server:
https://buildd.debian.org/status/package.php?p=gcr4
https://tests.reproducible-builds.org/debian/history/gcr4.html

I cherry-picked the fix to gcr which now shows the same result.

The particular test is not used in autopkgtests so that isn't a concern here.

Thank you,
Jeremy Bícha

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

From: Santiago Vila <sanvila@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>

Cc: Debian Release Team <debian-release@lists.debian.org>, 1057562@bugs.debian.org

Subject: Re: Some severities to reconsider due to flaky tests

Date: Wed, 9 Apr 2025 14:39:42 +0200

El 9/4/25 a las 14:26, Jeremy Bícha escribió:
>> Note that both gcr and gcr4 are key packages, so a serious severity
>> will not make the package to be removed.
> 
> It feels like there is less reason to argue about severity for gcr & gcr4 then?

Less reason to downgrade without asking RMs first, as you did.

Remember: we do not hide problems. Somebody should look at this bug
during Bug Squashing Parties, even if it does not make the package
to be removed.
 
>> A brief explanation for the maintainers that we don't want
>> flaky tests in trixie would also be nice.
> 
> "flaky" is vague and until there is a specific standard for failure
> rate, this is going to be subject to maintainer discretion to some
> degree.
> 
> As of 4.4.0.1, gcr4 does not appear to be flaky at all in the official
> buildds or on the reproducible builds server:

What happens in the buildds remains in the buildds. Whoever wants to
rebuild the package from source will not do so in the official buildds.

You are still violating Policy 4.2 for no particular reason.

If build-time dependencies are specified, it must be possible to build the package and produce > working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships).

We should not rely on a test which segfaults to determine if the package
is good or not. If the Release Managers still think this is ok
"because it works in the buildds", I can still call the TC for
your unwillingness to follow Debian Policy 4.2.

Please stop wasting everyone's time and disable the test which segfaults.
Do you need a patch for that?

Thanks.

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Santiago Vila <sanvila@debian.org>, 1057562@bugs.debian.org

Cc: Debian Release Team <debian-release@lists.debian.org>

Subject: Re: Bug#1057562: Some severities to reconsider due to flaky tests

Date: Wed, 9 Apr 2025 09:07:49 -0400

On Wed, Apr 9, 2025 at 8:42 AM Santiago Vila <sanvila@debian.org> wrote:
> What happens in the buildds remains in the buildds. Whoever wants to
> rebuild the package from source will not do so in the official buildds.
>
> You are still violating Policy 4.2 for no particular reason.
>
> If build-time dependencies are specified, it must be possible to build the package and produce > working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships).
>
> We should not rely on a test which segfaults to determine if the package
> is good or not. If the Release Managers still think this is ok
> "because it works in the buildds", I can still call the TC for
> your unwillingness to follow Debian Policy 4.2.

I do not believe Debian Policy is as precise on this detail as you
believe. It does not mandate that everything in Debian main be
buildable on a single CPU in an AWS instance.

> Do you need a patch for that?

I did help a bit in that trixie's debhelper by default now provides
verbose output for dh_auto_test even when passing. It looks like
something goes wrong in your builder at step 8 (
/gck/object/find_objects ) of the gcr:gck / object test. I am willing
to accept a patch to disable that subtest.

Thank you,
Jeremy Bícha

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

From: Santiago Vila <sanvila@debian.org>

To: 1057562@bugs.debian.org, Jeremy Bícha <jeremy.bicha@canonical.com>

Cc: control@bugs.debian.org

Subject: gcr4: FTBFS: failing tests

Date: Wed, 9 Apr 2025 16:17:47 +0200

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

tags 1057562 patch
thanks

Jeremy Bícha wrote:
> I am willing to accept a patch to disable that subtest.

Ok, please consider the attached patch (which I have actually tested).

I've tried to be neutral in the explanation without being too much specific.
In particular, the test does not only fail on machines with only one CPU.
I already noted that here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562#96

Thanks.

[gcr4.debdiff.txt (text/plain, attachment)]

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

From: Paul Gevers <elbrus@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, Santiago Vila <sanvila@debian.org>

Cc: Debian Release Team <debian-release@lists.debian.org>, 1057562@bugs.debian.org

Subject: Re: Some severities to reconsider due to flaky tests

Date: Wed, 9 Apr 2025 19:29:00 +0200

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

Hi all,

On 09-04-2025 14:26, Jeremy Bícha wrote:
> "flaky" is vague and until there is a specific standard for failure
> rate, this is going to be subject to maintainer discretion to some
> degree.


My personal standard (but with Release Team hat in mind) is that I file 
RC bugs about flakiness if a test fails more than about 1 out of 6 times 
(on a particular architecture if it's architecture specific).

Paul

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

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

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Paul Gevers <elbrus@debian.org>, 1057562@bugs.debian.org

Cc: Santiago Vila <sanvila@debian.org>, Debian Release Team <debian-release@lists.debian.org>

Subject: Re: Bug#1057562: Some severities to reconsider due to flaky tests

Date: Wed, 9 Apr 2025 15:42:22 -0400

On Wed, Apr 9, 2025 at 1:33 PM Paul Gevers <elbrus@debian.org> wrote:
>
> My personal standard (but with Release Team hat in mind) is that I file
> RC bugs about flakiness if a test fails more than about 1 out of 6 times
> (on a particular architecture if it's architecture specific).

What about if the failures happen 100% on someone's AWS instances but
are reliably passing on official Debian infrastructure?

Thank you,
Jeremy Bícha

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

From: Paul Gevers <elbrus@debian.org>

To: Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org, Santiago Vila <sanvila@debian.org>

Cc: Debian Release Team <debian-release@lists.debian.org>

Subject: Re: Bug#1057562: Some severities to reconsider due to flaky tests

Date: Thu, 10 Apr 2025 09:29:46 +0200

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

Hi,

On 09-04-2025 21:42, Jeremy Bícha wrote:
> On Wed, Apr 9, 2025 at 1:33 PM Paul Gevers <elbrus@debian.org> wrote:
>>
>> My personal standard (but with Release Team hat in mind) is that I file
>> RC bugs about flakiness if a test fails more than about 1 out of 6 times
>> (on a particular architecture if it's architecture specific).


Sorry, I didn't have the full context of the thread when I replied 
yesterday. I should have delayed sending the response until I did.

> What about if the failures happen 100% on someone's AWS instances but
> are reliably passing on official Debian infrastructure?


That's not what I mean with flaky.

For some background: in private communications that I've had with 
Santiago, he has been advocating the case to declare FTBFS that happen 
reliably on 1-cpu hosts as RC. From what I've seen so far in his 
reports, the 1-cpu case occasionally exposes bugs that are hidden 
otherwise on the official buildds and whatever the maintainer uses for 
their test builds (own machine, salsa, etc). Thus, using 1-cpu hosts is 
a valuable way to test. On the other hand, 1-cpu hosts are not what most 
developers (and users I assume) use, and also not what we use on the 
buildds. Hence I can also relate to maintainers that think the 1-cpu 
case is just odd. As a result, I have refused to back him up in filing 
the 1-cpu FTBFS type of bugs at RC level and I suggested to file these 
bugs at severity level important. I've told him however that I do expect 
maintainers to take reasonable (and hence maintainable) patches, which 
ideally should just go upstream of course. So I suggested he'd work on 
providing patches with the 1-cpu reports that he files, as the 1-cpu 
case is important to him. I've told Santiago multiple times I appreciate 
his QA rebuilds (including the 1-cpu ones) a lot.

So, back to this case. The original report (1057562) was filed at 
severity serious and didn't mention the 1-cpu case. Jeremy claimed 
flakiness and lowered severity, which was bumped later by a Release 
Manager with the request to avoid the flaky test (fix it or disable it) 
because it was seen on the buildds. Later on (after message 86) the 
severity discussion becomes more difficult, because of changes that 
probably lowered the chance of the bug on more-than-1-cpu hosts, the 
definition of flakiness and statistics on the buildds. My (Release Team 
member) position is the following. As mentioned earlier, flakiness in my 
book is a serious problem if the failure rate is above 1 out of 6 
(roughly). It's an important problem if it occurs less. On its own, 
1-cpu FTBFS are important issues but not serious. In this case, the 
FTBFS are due to a particular test, and luckily tests can be disabled 
during the build. The test fails reliably on the 1-cpu case, and when 
tested by Santiago on a 2-cpu system failed 8% of the cases. According 
to my limits above, that 8% is not RC, but because the FTBFS happens 
because of 1 test, I do ask the maintainers of gcr4 (and gcr) to disable 
that particular test during the build until the underlying problem has 
been fixed. The patch in message 121 is supposed to do exactly that.

Paul

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

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

From: Santiago Vila <sanvila@debian.org>

To: Paul Gevers <elbrus@debian.org>, Jeremy Bícha <jeremy.bicha@canonical.com>, 1057562@bugs.debian.org

Cc: Debian Release Team <debian-release@lists.debian.org>

Subject: Re: Bug#1057562: Some severities to reconsider due to flaky tests

Date: Thu, 10 Apr 2025 09:56:45 +0200

Thanks a lot for the summary.

Just a minor clarification.

El 10/4/25 a las 9:29, Paul Gevers escribió:

> So, back to this case. The original report (1057562) was filed at severity serious and didn't mention the 1-cpu case.

Did not mention the 1-cpu case because at the time it was failing very consistently on AWS machines
with 2 CPUs, and also in Salsa CI (see commit [cf9196b071b] that had to be reverted).

Thanks.

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

From: Jeremy Bícha <noreply@salsa.debian.org>

To: 1057562-submitter@bugs.debian.org

Subject: Bug#1057562 marked as pending in gcr4

Date: Sat, 12 Apr 2025 16:00:51 +0000

Control: tag -1 pending

Hello,

Bug #1057562 in gcr4 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/gcr4/-/commit/ba749e5a4d1ddc1ef748934b6db58bdd5e56b083

------------------------------------------------------------------------
Add patch to disable a test that segfaults on some systems

Closes: #1057562
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057562

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

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

To: 1057562-close@bugs.debian.org

Subject: Bug#1057562: fixed in gcr4 4.4.0.1-3

Date: Sat, 12 Apr 2025 16:15:24 +0000

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

Source: gcr4
Source-Version: 4.4.0.1-3
Done: Jeremy Bícha <jbicha@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
gcr4, 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 1057562@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha <jbicha@ubuntu.com> (supplier of updated gcr4 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: SHA512

Format: 1.8
Date: Sat, 12 Apr 2025 11:55:19 -0400
Source: gcr4
Built-For-Profiles: noudeb
Architecture: source
Version: 4.4.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Jeremy Bícha <jbicha@ubuntu.com>
Closes: 1057562
Changes:
 gcr4 (4.4.0.1-3) unstable; urgency=medium
 .
   [ Santiago Vila ]
   * Add patch to disable a test that segfaults on some systems
     (Closes: #1057562)
Checksums-Sha1:
 c8e9e9ec5913523229afde902895322a2a350b4c 3159 gcr4_4.4.0.1-3.dsc
 3c9af27ee311d10a3ef728a501dcb50745b83ffc 22980 gcr4_4.4.0.1-3.debian.tar.xz
 0efd6f8e5fe071b1ec3f0a5ab44030ff5d63b883 19369 gcr4_4.4.0.1-3_source.buildinfo
Checksums-Sha256:
 f8dba4991c4c7eb854e44e67b3955b385b61cfa1679f25b59a24d7d7686404b4 3159 gcr4_4.4.0.1-3.dsc
 b8b1ca8b9dd504fc691db15764ab83ac6a3c72f3784f4120e37d38d69fc84e09 22980 gcr4_4.4.0.1-3.debian.tar.xz
 76fe3298c051e1cd7a24cfe0502f9d36f82b1ba06502c458c3405f79b6259f36 19369 gcr4_4.4.0.1-3_source.buildinfo
Files:
 3421841c637fcf7713dedd5324dfb9b6 3159 gnome optional gcr4_4.4.0.1-3.dsc
 005d91ce0acf605a66cf71bb89d11403 22980 gnome optional gcr4_4.4.0.1-3.debian.tar.xz
 8e1d9f1dc87a59d32b6fcaa111292b06 19369 gnome optional gcr4_4.4.0.1-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmf6jh0ACgkQ5mx3Wuv+
bH04fg//SD1yt2NCXVsaHDBka0F6VdltR/POPRAYDHV8ioeVSc7qhYsNajxjEyi8
W62bU2WTNDlKNXJTjbJoUWfa0RcN+lGNFbLYZSnFLxbu5KcLxMAq1o/N9Gt145ek
JgeHVumA4fnt4umFazvJkRlMcGs4x5qh1FATal6dtatFCvIr05ChO55KJH74lceH
1uwIWfZoeUOrr9muaxtm6ffVMFAN8jk7iFOLRNj37aNQREEo8tZdpvRsKBbRX+uw
R1+G3xxCq8eHadBMPboVObkKmpD8yjYUOeKmGwCzOr3kXck+5IpPiyhnlZHH5hvo
On0LYkQnSz3JHKAyCOaMxPWeGlbQrOsQsQ/Udu68omz0Ce+Mk1hY/SfgeYwdCw6M
d3f9OpEKEmJbw6ZwvjgPs2ymPIxUS6s0pJ1y+2VIcALsVuEisKXzHE2vdqwOUNWx
X6uVueLPeMJBHf+I6nfZaWMkuJ1KN0Drvu/a1wDw0c7KcYt1m/iOhWogTgKf3o7G
Bn6pQ0MW+DK2qtNba+HUEltpaOSk/gkXyPZ2FFZEpaGZek6hABiy+lwa+qg9i5Hw
Bx5FMQ/lTXELJv0L7VYlp4MCzAeNfcjBDoa35pgyMP/pFirbhI2QC+jwRchEg9cS
GJVesKluMEmoy3lYgcaM4+TMlHWRCljkdKxoue7+IMby4QIY6sE=
=2OeK
-----END PGP SIGNATURE-----

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

Send a report that this bug log contains spam.