← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1830479] Re: testcases expect first kernel log line, but not always in logs

 

It's a critical but in the Ubuntu platform if the very first kernel log
line is not available in the system logs.

And it is present on all arches, apart from the identified buggy arm64
which is in-flight being fixed (in eoan-proposed & disco-proposed with
other releases to follow).

cmdline-upstart-boot is only present in xenial? and arm64-kvm testing
only started to be done post xenial release. Hence systemd/arm64
autopkgtest status is currently "Always Failed" and doesn't block
anything.

This is not applicable to devel series, nor should be applied in prior
releases, instead kernel should be fixed.

** Changed in: systemd (Ubuntu Eoan)
       Status: New => Won't Fix

** Changed in: systemd (Ubuntu Disco)
       Status: New => Won't Fix

** Changed in: systemd (Ubuntu Xenial)
       Status: New => Won't Fix

-- 
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:
  Won't Fix
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
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