[Bug 1992178] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From sthoufee at in.ibm.com 2023-06-06 01:35 EDT-------
(In reply to comment #6)
> Backtraces are on the upstream bug, eg:
>
> https://github.com/systemd/systemd/issues/25091#issuecomment-1401824195
> https://github.com/systemd/systemd/issues/25091#issuecomment-1402425787
>
> It would be better if the IBM developers could engage directly on the
> upstream ticket for the initial investigation, given the information is
> recorded there. Thanks!

Peter, Could you check this upstream bug and confirm if this needs to be
looked by tools chain team as claimed by Ubuntu distro team?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1992178

Title:
  autopkgtest: upstream tests that run in qemu hang on ppc64el

Status in systemd:
  Unknown
Status in The Ubuntu-power-systems project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New

Bug description:
  I believe this started early in the kinetic cycle, cf.
  https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs
  https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el.
  Timeouts in the upstream tests have been an issue for a while, but
  kinetic on ppc64el consistently times out with upstream tests that run
  in QEMU.

  Skipping individual tests does not help, because *which* tests time
  out appears to change with each build. For example, in 251.4-1ubuntu4
  the TEST-36-NUMAPOLICY test was consistently the culprit, but now in
  251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out.

  I have not been able to identify a root cause for this, but it seems
  that running tests in QEMU is very fragile on ppc64el, where as the
  tests that run in nspawn are more consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1992178/+subscriptions