FTR, I would strongly advise against that, see https://github.com/martinpitt/umockdev/issues/110#issuecomment-736224503 . You want the tests to work independently on the hardware it's running on, so that you can run it on e.g. standard autopkgtest infra.
You could create /sys/firmware/efi/efivars/ tarballs of a bunch of real systems with the properties that you want, keep them in the tests, and unpack these in your test cases. You most probably just need a few of them, so you can strip them down or possibly create them individually as files, but a full tarball might be the quickest start. ** Bug watch added: github.com/martinpitt/umockdev/issues #110 https://github.com/martinpitt/umockdev/issues/110 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1906320 Title: fake-device-wrapper should bind-mount efivars Status in ubuntu-drivers-common package in Ubuntu: New Bug description: /usr/share/ubuntu-drivers-common/fake-devices-wrapper should bindmount efivars under testbed.get_root_dir(). Ie. such that /sys/firmware/efi/efivars is correctly available under the umockdev test-bed. That way when testing subiquity, it should correctly observe if it was booted under secureboot, or not. Or maybe we can create a few options to fake-devices-wrapper whether or not to present Secureboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1906320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
