[Bug 1994143] Re: fwupd 1.7.9 armhf test failure

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
       Status: New

** Changed in: oem-priority
     Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

** Tags added: oem-priority

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
       Status: New => Confirmed

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

Title:
  fwupd 1.7.9 armhf test failure

Status in OEM Priority Project:
  Confirmed
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Committed
Status in fwupd source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The armhf autopkgtest for fwupd is failing reliably. This is a test
  issue.

  The error is

  FuPluginMtd:ERROR:../plugins/mtd/fu-self-test.c:50:fu_test_mtd_device_func: assertion failed (error == NULL): failed to open /dev/mtd0: No such file or directory (g-io-error-quark, 1)
  Bail out! FuPluginMtd:ERROR:../plugins/mtd/fu-self-test.c:50:fu_test_mtd_device_func: assertion failed (error == NULL): failed to open /dev/mtd0: No such file or directory (g-io-error-quark, 1)
  Aborted (core dumped)

  This has been now fixed in kinetic and needs to be backported to focal
  and jammy.

  [Test Case]

  Run autopkgtests and make sure all architectures pass once again.

  [Regression Potential]

  Fix only in the tests, so there should be no risk for runtime. Worst
  regression would be that the test changes regress the tests, making us
  miss real issues. But that's rather unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994143/+subscriptions