517s =================================== FAILURES =================================== 517s ________________ TestApportValgrind.test_valgrind_min_installed ________________ 517s 517s self = <tests.integration.test_apport_valgrind.TestApportValgrind testMethod=test_valgrind_min_installed> 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s =============================== warnings summary ===============================
Full log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble- bdrung-ppa/noble/armhf/a/apport/20231116_191750_27834@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed Status in apport package in Ubuntu: New Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s =================================== FAILURES =================================== 638s ________________ TestApportValgrind.test_valgrind_min_installed ________________ 638s 638s self = <tests.integration.test_apport_valgrind.TestApportValgrind testMethod=test_valgrind_min_installed> 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp