Bug#929730: systemd: boot-and-services test expects first kernel log line, but not always in logs

[Dan Streetman]

On Wed, May 29, 2019 at 12:35 PM Michael Biebl <biebl at debian.org> wrote:
>
> Am 29.05.19 um 18:19 schrieb Dan Streetman:
> > Package: systemd
> > Version: 241-5
> > Severity: normal
> > Tags: patch
> > User: ubuntu-devel at lists.ubuntu.com
> > Usertags: origin-ubuntu eoan ubuntu-patch
> >
> > Dear Maintainer,
> >
> > boot-and-services test expects the first(ish) kernel log line to be in the system logs, but that is not guaranteed to be in the logs.
> >
> > -- Package-specific info:
> >
> >
> >   * d/t/boot-and-services:
> >     - don't fail if some kernel msgs are missed (LP: #1830479)
>
>
> Afair, this is due to the kernel ring buffer being too small (on arm64)
> Wouldn't it be better to address that? After all, you also want early
> boot messages when running systemd in production.

that's one reason; is systemd missing kernel messages due to no fault
of its own really something that should fail the test case?

note that unless systemd-journald explicitly noted that kernel
messages were missed, it still checks for the command-line kernel line

>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>