Your message dated Sun, 14 Dec 2025 02:40:48 +0000
with message-id <[email protected]>
and subject line Bug#1114756: fixed in openmsx 21.0+dfsg-1
has caused the Debian Bug report #1114756,
regarding openmsx: flaky autopkgtest 'run' on multiple architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1114756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114756
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: openmsx
Version: 20.0+dfsg-1.2
Severity: important
Justification: https://release.debian.org/testing/rc_policy.txt ยง6a
User: [email protected]
Usertags: flaky
Control: affects -1 + src:libsdl2

The autopkgtest for openmsx intermittently fails on ci.debian.net, 
especially on slower architectures:

https://ci.debian.net/packages/o/openmsx/testing/armhf/
https://ci.debian.net/packages/o/openmsx/testing/riscv64/

but also occasionally on fast architectures:

https://ci.debian.net/packages/o/openmsx/testing/amd64/ (2025-08-13 02:35:57 
UTC)
https://ci.debian.net/packages/o/openmsx/testing/arm64/ (2025-08-13 19:09:33 
UTC)

Looking at the logs, 'unit' seems to be generally reliable, and it's 
'run' that intermittently fails.

The testing migration infrastructure assumes this is a regression in a 
package that was upgraded, preventing packages like libsdl2 from 
migrating to testing until the openmsx autopkgtest is retried. I'm 
reporting this as non-RC for now because it isn't *that* bad (certainly 
not as bad as uqm, which I have to retry on riscv64 for basically every 
libsdl2 upload), but it's likely to be escalated to RC if it becomes a 
practical problem for migrations.

If this test is expected to be unreliable, please mark it with 
"Restrictions: flaky" so that it isn't used to gate migrations from 
unstable to testing:

    Tests: run
    Depends: ...
    Restrictions: allow-stderr, flaky

Or it could be marked with the "skippable" restriction:

    Tests: run
    Depends: ...
    Restrictions: allow-stderr, skippable

and do its own logic to classify its results into three buckets, using 
an exit status convention borrowed from Autotools:

* success: exit 0
* skipped, expected/ignorable failure or other neutral status: exit 77
* failure: any other exit status

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: openmsx
Source-Version: 21.0+dfsg-1
Done: Bas Wijnen <[email protected]>

We believe that the bug you reported is fixed in the latest version of
openmsx, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Wijnen <[email protected]> (supplier of updated openmsx 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 14 Dec 2025 02:30:41 +0100
Source: openmsx
Architecture: source
Version: 21.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Bas Wijnen <[email protected]>
Changed-By: Bas Wijnen <[email protected]>
Closes: 1114756 1121755
Changes:
 openmsx (21.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1114756, #1121755)
   * Removed and updated patches that were (partially) applied upstream.
   * Updated Standards-Version to 4.7.2. (No changes needed.)
   * Removed Suggests for obsolete openmsx-catapult and openmsx-debugger.
Checksums-Sha1:
 5e15a60e3d8d06918d2b8748f8d0a82284c847c6 2136 openmsx_21.0+dfsg-1.dsc
 70ff09bca95ef6e93511bb041f7415465f13f577 6115764 openmsx_21.0+dfsg.orig.tar.xz
 bdf3d5b474a760169b699fc9085368e0273570a7 18760 
openmsx_21.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
 e3a595fc0059dce3f91ecd52561c014bc452acd1052b307474411421b4a357f8 2136 
openmsx_21.0+dfsg-1.dsc
 96436de615e1cab0197c80c701e61fd02f31d81c0c84c13251c2525e0a2d7773 6115764 
openmsx_21.0+dfsg.orig.tar.xz
 e6390eab002203153f7d7676acd0fd0b2515cdb796e6c3b63137334eb5a9ffa1 18760 
openmsx_21.0+dfsg-1.debian.tar.xz
Files:
 14d96dd29738d205b21a374e5c72bbe3 2136 otherosfs optional 
openmsx_21.0+dfsg-1.dsc
 35957340914f4d9695a0293aa7fb0581 6115764 otherosfs optional 
openmsx_21.0+dfsg.orig.tar.xz
 3fbd70d68dedea5bb521a27240bcd2f5 18760 otherosfs optional 
openmsx_21.0+dfsg-1.debian.tar.xz

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

iQJGBAEBCgAwFiEEKI9JSvHOfJKJyDQanNF9WAfAcToFAmk+GM8SHHdpam5lbkBk
ZWJpYW4ub3JnAAoJEJzRfVgHwHE6SroP/1ttNRqmJuE8FKHL1EMZ/tLe47a5J3sI
TL1hmL1Uiv4RonyORlt5rCt3HmKiVw9YbQMwWL1ua5UVMU/xzGkI/4kBhXbLaKeE
p7SFyrzwaEoXLZ1Gi/JY/D2CKy8e3IhA4xgc6O9uV12DXykU2ppnEhvLGEI63cNX
wTH2/9Krdqv9zEJo03ZCSAGbYlllvLEHMqDKdaa3Ai5P/cv81uQceJW+Itw4fVvC
bCWMUVf0n5oz+gVHfvw36XtIraCqzagBlofsx3RWIQt1lGFuZLBqYzyLzZx3nna9
iG4XKsLjxWU5s6fZp290QKOKrfANtWvAZrEumZcT86yP03Toa53YVQ74pvk8pqei
s2BZfF++Xl+M9h9ZFVyShOzKgi6AKyydbewAwzSKHXP0tll7jw/9TogSax7Sa7ou
72kFWHAUJrAtRAwKQFpC0HtiF/C5KmfZluQ4xVFnup8e1WgNNs/BdODJsvu7q5Gn
eyJwLYyYBk0CFQyVYCR2McQFcRxM7JtAkKn0a2GDeOjQ13ORmeCJAX2UhTSmo+GH
XJBZGDA5l+YpdWd2zwWv+uo90TGuXeqZ92jzmlc/yKn23UScm7rhOcD1GT5Bbayi
TnYgoNpiYPI1iG3C8M1ihGgccTJW3tjbLjQUyvUaLGe8qaWJewn0uPPs5jySh6DV
JjDm3ko+D1zF
=iM1X
-----END PGP SIGNATURE-----

Attachment: pgpruwY4TqzRJ.pgp
Description: PGP signature


--- End Message ---

Reply via email to