group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #30497
[Bug 1830479] Re: testcases expect first kernel log line, but not always in logs
** Bug watch added: Debian Bug tracker #929730
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929730
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929730
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1830479
Title:
testcases expect first kernel log line, but not always in logs
Status in systemd package in Ubuntu:
New
Status in systemd source package in Xenial:
New
Status in systemd source package in Bionic:
New
Status in systemd source package in Cosmic:
New
Status in systemd source package in Disco:
New
Status in systemd source package in Eoan:
New
Status in systemd package in Debian:
Unknown
Bug description:
[impact]
boot-and-services and cmdline-upstart-boot expect the first(ish)
kernel log line to be in the system logs, but that is not guaranteed
to be in the logs.
[test case]
run autopkgtest on arm64 with the current kernel, whose kernel log
size is too small for journald or rsyslogd to capture the first kernel
log messages.
[regression potential]
low; testcase fix only.
[other info]
the specific cause of this currently is too-small kernel log buffer
size on arm64, which is being fixed in bug 1824864, but increasing
amounts of boot time logging may cause a failure again, or custom
kernel configs with small log buffers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830479/+subscriptions