Your message dated Tue, 04 Mar 2025 11:19:32 +0000 with message-id <e1tpqja-001eyi...@fasolo.debian.org> and subject line Bug#1099085: fixed in apparmor 4.1.0~beta5-3 has caused the Debian Bug report #1099085, regarding apparmor: FTBFS on riscv64: subprocess.TimeoutExpired to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1099085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: apparmor Version: 4.1.0~beta5-2 Severity: serious Tags: ftbfs patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear Maintainer, Now apparmor has one FTBFS issue on riscv64 due to timeout on test case: ``` ... ERROR: test_allow_all (__main__.TestLogprof.test_allow_all) ---------------------------------------------------------------------- Traceback (most recent call last): File "/build/reproducible-path/apparmor-4.1.0~beta5/utils.python3.13/test/test-logprof.py", line 129, in test_allow_all self.process.wait(timeout=0.3) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.13/subprocess.py", line 1276, in wait return self._wait(timeout=timeout) ~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/subprocess.py", line 2060, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3.13', '../aa-logprof', '--allow-all', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-aj9tsnoi/profiles', '--no-check-mountpoint', '--output-dir', '/tmp/aa-test-aj9tsnoi']' timed out after 0.3 seconds ... ``` Full log please to see here: https://buildd.debian.org/status/fetch.php?pkg=apparmor&arch=riscv64&ver=4.1.0%7Ebeta5-2&stamp=1740485392&raw=0 The fixing is very easy and it works on my local Unmatched board, but I am not sure if it's appropriate to send this patch given there is one beta hint on uploading. Unfortunately, it was failed to build again during python3.13, this may block something. So could you have a look at this? Please let me know if any issues. -- Regards, -- Bo YUdiff -Nru apparmor-4.1.0~beta5/debian/changelog apparmor-4.1.0~beta5/debian/changelog --- apparmor-4.1.0~beta5/debian/changelog 2025-02-20 20:41:37.000000000 +0000 +++ apparmor-4.1.0~beta5/debian/changelog 2025-02-27 02:23:26.000000000 +0000 @@ -1,3 +1,10 @@ +apparmor (4.1.0~beta5-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Increase the timeout on riscv64 to pass test cases. (Closes: #-1) + + -- Bo YU <vi...@debian.org> Thu, 27 Feb 2025 02:23:26 +0000 + apparmor (4.1.0~beta5-2) unstable; urgency=medium * Revert "gbp.conf: set debian-branch to debian/experimental" diff -Nru apparmor-4.1.0~beta5/debian/patches/increase-test-timeout-rv64.patch apparmor-4.1.0~beta5/debian/patches/increase-test-timeout-rv64.patch --- apparmor-4.1.0~beta5/debian/patches/increase-test-timeout-rv64.patch 1970-01-01 00:00:00.000000000 +0000 +++ apparmor-4.1.0~beta5/debian/patches/increase-test-timeout-rv64.patch 2025-02-27 02:22:57.000000000 +0000 @@ -0,0 +1,22 @@ +--- a/utils/test/test-logprof.py ++++ b/utils/test/test-logprof.py +@@ -14,6 +14,7 @@ + import subprocess + import sys + import unittest ++import platform + + # import apparmor.aa as aa # see the setup_aa() call for details + from common_test import AATest, read_file, setup_all_loops # , setup_aa +@@ -126,7 +127,10 @@ + output = self.process.stdout.readline().decode("utf-8").strip() + self.assertEqual(output, line) + # give logprof some time to write the updated profile and terminate +- self.process.wait(timeout=0.3) ++ if platform.machine() == 'riscv64': ++ self.process.wait(timeout=0.6) ++ else: ++ self.process.wait(timeout=0.3) + self.assertEqual(self.process.returncode, 0) + + diff -Nru apparmor-4.1.0~beta5/debian/patches/series apparmor-4.1.0~beta5/debian/patches/series --- apparmor-4.1.0~beta5/debian/patches/series 2025-02-20 20:41:37.000000000 +0000 +++ apparmor-4.1.0~beta5/debian/patches/series 2025-02-27 02:20:17.000000000 +0000 @@ -9,3 +9,4 @@ # ubuntu/mimeinfo-snap-support.patch # ubuntu/profiles-grant-access-to-systemd-resolved.patch # ubuntu/enable-pinning-of-pre-AppArmor-3.x-poli.patch +increase-test-timeout-rv64.patch
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: apparmor Source-Version: 4.1.0~beta5-3 Done: intrigeri <intrig...@debian.org> We believe that the bug you reported is fixed in the latest version of apparmor, 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 1099...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. intrigeri <intrig...@debian.org> (supplier of updated apparmor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 04 Mar 2025 10:52:41 +0000 Source: apparmor Architecture: source Version: 4.1.0~beta5-3 Distribution: unstable Urgency: medium Maintainer: Debian AppArmor Team <pkg-apparmor-t...@lists.alioth.debian.org> Changed-By: intrigeri <intrig...@debian.org> Closes: 1099085 Changes: apparmor (4.1.0~beta5-3) unstable; urgency=medium . * upstream-mr-1558-avoid-blhc-false-positive.patch: new patch * upstream-mr-1567-fix-riscv64.patch: new patch (Closes: #1099085). Thanks to Bo YU for the patch. Checksums-Sha1: c7a0b8f2ca287c297f2e1946049148ccdeeffb9d 3336 apparmor_4.1.0~beta5-3.dsc 80b7ea8401eb2cf090c3f2d04979e837b0dec328 93588 apparmor_4.1.0~beta5-3.debian.tar.xz Checksums-Sha256: 4ecf659e6f4216fa8c59fefcbc9ec43fc23f31f0d64763e0f393e995c946c349 3336 apparmor_4.1.0~beta5-3.dsc 320d92782b897517ecfbadc36f4f74bc4ed5be99360fa70349ec15ecc0ba2d2e 93588 apparmor_4.1.0~beta5-3.debian.tar.xz Files: e425024f5bea4165e0c01d51017f0d4c 3336 admin optional apparmor_4.1.0~beta5-3.dsc de6485edc6baa8f38c7ec0bf32bc1810 93588 admin optional apparmor_4.1.0~beta5-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iIsEARYKADMWIQRhtDRcZu/HkP7YWcafj6cvaVTDowUCZ8beoxUcaW50cmlnZXJp QGRlYmlhbi5vcmcACgkQn4+nL2lUw6M0eAEA+nWkbFMgtMVvria1J2pe8/6xMnRX 2f5lRndPZVEpZtoBANmBanq0XEwKKsWk4JqXomuc2V7qDa3D7QW0uy4kb1MH =CsH+ -----END PGP SIGNATURE-----
Description: PGP signature
--- End Message ---
