Comment 14 for bug 1979963

I looked at some of the kinetic test history (https://autopkgtest.ubuntu.com/packages/fwupd/kinetic/armhf) and find that there are some passes and some fails there with exact same package.

Failure was in #13 above, but a pass looks like this:
# FuQuirks-DEBUG: ignoring: The resource at ?/org/freedesktop/fwupd? does not exist
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
# XbSilo-DEBUG: attempting to load /tmp/.9W13P1
# XbSilo-DEBUG: failed to load silo: blob too small
# FuQuirks-DEBUG: no quirk data, not creating prepared queries
ok 1 /mtd/device # SKIP could not find mtdram device

Furthermore earlier in the "fail" log you can see:

> FuEngine failed to add device /sys/devices/virtual/mtd/mtd0: failed to open /dev/mtd0: No such file or directory

In both logs I notice (fail/pass)

modprobe: FATAL: Module mtdram not found in directory /lib/modules/5.4.0-122-generic
and
modprobe: FATAL: Module mtdram not found in directory /lib/modules/5.4.0-109-generic

Because of this I don't believe we should interpret this test result as a failure. If we don't have the mtdram module loaded for autopkgtest (https://github.com/fwupd/fwupd/blob/main/contrib/debian/tests/ci#L4) then how can we possibly be runing mtdram tests?

Please waive this for the purpose of the SRU.