** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to