Your message dated Sat, 1 Jan 2022 22:17:44 +0100
with message-id <[email protected]>
and subject line Re: systemd: boot-and-services testsuite failure on armhf
has caused the Debian Bug report #982928,
regarding systemd: boot-and-services testsuite failure on armhf
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.)
--
982928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982928
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: systemd
Version: 247.3-1
Severity: minor
Dear Maintainer,
Salsa latest version of autopkgtest adds armhf qemu testbed.
autopkgtest-virt-qemu --dpkg-architecture=armhf on systemd
fails on boot-and-service. Failure happens at boot-and-service.
The relevant log is as follows. It seems that the error message
is different from what is expected by testsuite script...
17:test_bash_crash (__main__.CoredumpTest) ... FAIL
41:FAIL: test_bash_crash (__main__.CoredumpTest)
44: File
"/tmp/autopkgtest.XllwP8/build.pib/src/debian/tests/boot-and-services", line
457, in test_bash_crash
45: self.assertRegex(journal, b'#[0-9] .*bash')
46:AssertionError: Regex didn't match: b'#[0-9] .*bash' not found in b'--
Journal begins at Sun 2021-02-14 16:04:21 UTC, ends at Sun 2021-02-14 16:09:03
UTC. --\nFeb 14 16:09:03 host systemd-coredump[835]: Process 833 (bash) of user
0 dumped core.\n \n
Stack trace of thread 833:\n
#0 0x00000000b6eba0e8 kill (libc.so.6 + 0x2a0e8)\n'
Best regards, Ryutaroh Matsumoto
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Kernel: Linux 5.10.0-3-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.139
ii libnss-systemd 247.3-1
ii libpam-systemd 247.3-1
ii udev 247.3-1
-- no debconf information
boot-and-services.tar.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
On Wed, 07 Jul 2021 22:01:26 +0200 Michael Biebl <[email protected]> wrote:
Control: tags -1 + moreinfo
On Wed, 17 Feb 2021 02:56:52 +0900 Ryutaroh Matsumoto
<[email protected]> wrote:
> Source: systemd
> Version: 247.3-1
> Severity: minor
>
> Dear Maintainer,
>
> Salsa latest version of autopkgtest adds armhf qemu testbed.
> autopkgtest-virt-qemu --dpkg-architecture=armhf on systemd
> fails on boot-and-service. Failure happens at boot-and-service.
> The relevant log is as follows. It seems that the error message
> is different from what is expected by testsuite script...
>
> 17:test_bash_crash (__main__.CoredumpTest) ... FAIL
> 41:FAIL: test_bash_crash (__main__.CoredumpTest)
> 44: File "/tmp/autopkgtest.XllwP8/build.pib/src/debian/tests/boot-and-
services", line 457, in test_bash_crash
> 45: self.assertRegex(journal, b'#[0-9] .*bash')
> 46:AssertionError: Regex didn't match: b'#[0-9] .*bash' not found in b'--
Journal begins at Sun 2021-02-14 16:04:21 UTC, ends at Sun 2021-02-14
16:09:03 UTC. --\nFeb 14 16:09:03 host systemd-coredump[835]: Process 833
(bash) of user 0 dumped core.\n
\n Stack trace of thread
833:\n #0 0x00000000b6eba0e8
kill (libc.so.6 + 0x2a0e8)\n'
Is this still reproducible with v249 from experimental?
If so, can you please forward this issue to the arm porters and tag the bug
report accordingly. So far, this looks like an armhf and/or qemu specific
problem to me. But lacking the necessary hardware / test environment, I can
debug this.
Let's close this at this point. I don't see value in keeping it open
unless there is someone who has the necessary hardware and interest to
further investigate this, in which case we can reopen it.
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
