[Bug 2054450] [NEW] apport arm64 autopkgtest flaky
Julian Andres Klode
2054450 at bugs.launchpad.net
Tue Feb 20 16:05:49 UTC 2024
Public bug reported:
The following failure can sometimes be observed on arm64 in noble, for
example, with gnupg2 and sensible-utils:
360s =================================== FAILURES ===================================
360s __________________________ T.test_core_dump_packaged ___________________________
360s
360s self = <tests.integration.test_signal_crashes.T testMethod=test_core_dump_packaged>
360s
360s def test_core_dump_packaged(self):
360s """Packaged executables create core dumps on proper ulimits."""
360s # for SEGV and ABRT we expect reports and core files
360s for sig in (signal.SIGSEGV, signal.SIGABRT):
360s for kb, exp_file in core_ulimit_table:
360s resource.setrlimit(resource.RLIMIT_CORE, (kb, -1))
360s self.do_crash(
360s expect_corefile=exp_file,
360s expect_corefile_owner=os.geteuid(),
360s sig=sig,
360s )
360s > self.check_report_coredump(self.test_report)
360s
360s /tmp/autopkgtest.pa788q/autopkgtest_tmp/tests/integration/test_signal_crashes.py:413:
360s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
360s /tmp/autopkgtest.pa788q/autopkgtest_tmp/tests/integration/test_signal_crashes.py:1114: in check_report_coredump
360s self.assertIn("\n#2", r.get("Stacktrace"))
360s E AssertionError: '\n#2' not found in '#0 0x0000fffff7fd6428 in ?? ()\nNo symbol table info available.\n#1 0x0000fffff7ffd000 in ?? ()\nNo symbol table info available.\nBacktrace stopped: previous frame inner to this frame (corrupt stack?)'
360s ----------------------------- Captured stderr call -----------------------------
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory
360s warning: target file /proc/4152/cmdline contained unexpected null characters
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory
360s warning: target file /proc/4228/cmdline contained unexpected null characters
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory
360s warning: target file /proc/4308/cmdline contained unexpected null characters
360s warning: 1972 ./elf/dl-load.c: No such file or directory
360s warning: target file /proc/4388/cmdline contained unexpected null characters
360s warning: 1972 ./elf/dl-load.c: No such file or directory
360s warning: target file /proc/4463/cmdline contained unexpected null characters
360s warning: 1150 ./elf/rtld.c: No such file or directory
360s warning: target file /proc/4539/cmdline contained unexpected null characters
360s =============================== warnings summary ===============================
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054450
Title:
apport arm64 autopkgtest flaky
Status in apport package in Ubuntu:
New
Bug description:
The following failure can sometimes be observed on arm64 in noble, for
example, with gnupg2 and sensible-utils:
360s =================================== FAILURES ===================================
360s __________________________ T.test_core_dump_packaged ___________________________
360s
360s self = <tests.integration.test_signal_crashes.T testMethod=test_core_dump_packaged>
360s
360s def test_core_dump_packaged(self):
360s """Packaged executables create core dumps on proper ulimits."""
360s # for SEGV and ABRT we expect reports and core files
360s for sig in (signal.SIGSEGV, signal.SIGABRT):
360s for kb, exp_file in core_ulimit_table:
360s resource.setrlimit(resource.RLIMIT_CORE, (kb, -1))
360s self.do_crash(
360s expect_corefile=exp_file,
360s expect_corefile_owner=os.geteuid(),
360s sig=sig,
360s )
360s > self.check_report_coredump(self.test_report)
360s
360s /tmp/autopkgtest.pa788q/autopkgtest_tmp/tests/integration/test_signal_crashes.py:413:
360s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
360s /tmp/autopkgtest.pa788q/autopkgtest_tmp/tests/integration/test_signal_crashes.py:1114: in check_report_coredump
360s self.assertIn("\n#2", r.get("Stacktrace"))
360s E AssertionError: '\n#2' not found in '#0 0x0000fffff7fd6428 in ?? ()\nNo symbol table info available.\n#1 0x0000fffff7ffd000 in ?? ()\nNo symbol table info available.\nBacktrace stopped: previous frame inner to this frame (corrupt stack?)'
360s ----------------------------- Captured stderr call -----------------------------
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory
360s warning: target file /proc/4152/cmdline contained unexpected null characters
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory
360s warning: target file /proc/4228/cmdline contained unexpected null characters
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory
360s warning: target file /proc/4308/cmdline contained unexpected null characters
360s warning: 1972 ./elf/dl-load.c: No such file or directory
360s warning: target file /proc/4388/cmdline contained unexpected null characters
360s warning: 1972 ./elf/dl-load.c: No such file or directory
360s warning: target file /proc/4463/cmdline contained unexpected null characters
360s warning: 1150 ./elf/rtld.c: No such file or directory
360s warning: target file /proc/4539/cmdline contained unexpected null characters
360s =============================== warnings summary ===============================
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2054450/+subscriptions
More information about the foundations-bugs
mailing list