Yes, I like this approach much better. LGTM! I'd also suggest to call "modprobe mtdram" prior to running the tests, so that the new mtd test are actually executed. See attached debdiff.
This way it works for arm64 (skipping the test due to mtd0 not being provided by mtdram) and works for non-arm64 (using modprobe, as suggested above) https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-slyon- testing/kinetic/arm64/f/fwupd/20220517_123619_edd79@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-slyon- testing/kinetic/amd64/f/fwupd/20220517_122000_38022@/log.gz WDYT? Can we upload it this way? ... Actually, we might want to do "modprobe mtdram || true" as this is basically optional. ** Patch added: "2-fix-mtd-tests.debdiff" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+attachment/5590388/+files/2-fix-mtd-tests.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973598 Title: mtd-self-test failure on arm64 (mtdram module) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1973598/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
