Hi Andreas,
On Tue, Mar 18 2025, Andreas Metzler wrote:
> t06_publish ➔ PublishSnapshot38Test ... FAIL 17s
> [...]
> raise Exception("content doesn't match:\n" + diff + "\n")
> Exception: content doesn't match:
> ---
> +++
> @@ -1,7 +1,7 @@
> +Signing file 'main_installer-s390x_current_images_SHA256SUMS' with gpg,
> please enter your passphrase when prompted:
> Loading packages...
> Generating metadata files and linking package files...
> Finalizing metadata files...
> -Signing file 'main_installer-s390x_current_images_SHA256SUMS' with gpg,
> please enter your passphrase when prompted:
> Signing file 'Release' with gpg, please enter your passphrase when prompted:
> Clearsigning file 'Release' with gpg, please enter your passphrase when
> prompted:
>
> ---------------------------------------
>
> Afaict the message "Signing file
> 'main_installer-s390x_current_images_SHA256SUMS' with gpg [...]" shows
> up a little bit earlier and the testsuite is unhappy with that. Is this
> really an issue on the gpg side?
I'll check with the upstream author. If the conclusion is that this test
is a somewhat flaky, I could always disable it if that helps out with (I
assume) a regression on your end?
Cheers,
--
Seb
