Verified successful autopkgtest on https://autopkgtest.ubuntu.com/packages/apport for 2.28.1-0ubuntu3.3:
* amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/a/apport/20241114_155914_7aded@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/a/apport/20241114_152854_d2cf5@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/a/apport/20241114_153245_54069@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/a/apport/20241114_153720_f72b7@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/a/apport/20241114_152611_b90ee@/log.gz All test were successful, except for these tests on s390x: ``` FAILED tests/unit/test_problem_report.py::T::test_modify FAILED tests/unit/test_report.py::T::test_report_from_systemd_coredump_storage_journal FAILED tests/integration/test_problem_report.py::T::test_big_file FAILED tests/integration/test_problem_report.py::T::test_write_file ``` These four test failures are caused by bug #2076269 which I will address in a future SRU (summary: it's a flaw of the test, but not the non-test code). ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- 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/2073933 Title: tests/integration/test_signal_crashes.py::T::test_core_dump_packaged fails on armhf Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Noble: Fix Committed Bug description: [ Impact ] The Apport 2.29.0 test case `tests/integration/test_signal_crashes.py::T::test_core_dump_packaged` can fail on armhf: ``` 394s =================================== FAILURES =================================== 394s __________________________ T.test_core_dump_packaged ___________________________ 394s 394s self = <tests.integration.test_signal_crashes.T testMethod=test_core_dump_packaged> 394s 394s def test_core_dump_packaged(self): 394s """Packaged executables create core dumps on proper ulimits.""" 394s # for SEGV and ABRT we expect reports and core files 394s for sig in (signal.SIGSEGV, signal.SIGABRT): 394s for kb, exp_file in core_ulimit_table: 394s resource.setrlimit(resource.RLIMIT_CORE, (kb, -1)) 394s self.do_crash( 394s expect_corefile=exp_file, 394s expect_corefile_owner=os.geteuid(), 394s sig=sig, 394s ) 394s > self.check_report_coredump(self.test_report) 394s 394s /tmp/autopkgtest.GVBNRi/autopkgtest_tmp/tests/integration/test_signal_crashes.py:426: 394s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 394s /tmp/autopkgtest.GVBNRi/autopkgtest_tmp/tests/integration/test_signal_crashes.py:1216: in check_report_coredump 394s self.assertIn("\n#2", r.get("Stacktrace")) 394s E AssertionError: '\n#2' not found in '#0 0xf7fe2734 in ?? ()\nNo symbol table info available.\n#1 0xf7fef000 in ?? ()\nNo symbol table info available.\nBacktrace stopped: previous frame identical to this frame (corrupt stack?)' ``` Full log: https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/armhf/a/apport/20240618_034715_7581f@/log.gz [ Test Plan ] Check that the fixed Apport does not have failing unit-and- integration-tests autopkgtests on all archs. [ Where problems could occur ] The fix only touches test code. It could only affect the test results, but not code installed on the users machines. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2073933/+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
