dm-writeboost-dkms: prevent running autopkgtest on small systems

[Andrea Righi]

[Impact]

dm-writeboost-dkms autopkgtest is quite I/O intensive, it needs 14G of disk and it runs the hdd stress-ng stressor for 5min.

This can really hog some testing servers, due the high amount of I/O and typically this test is flaky in our testing infrastructure because there's not enough available disk space to perform the test.

[Test case]

Run dm-writeboost-dkms autopkgtest, for example:

 $ apt source dm-writeboost-dkms
 $ cd dm-writeboost-2.2.16
 $ sudo autopkgtest . -- null

Expected result in small systems with the fix applied should look like the following:

 test-dm-writeboost.sh SKIP exit status 77 and marked as skippable

[Fix]

Set the test as skippable and change the test to exit 77 if the testing system is too small (e.g., not enough available disk space or cpus < 8).

[Regression potential]

With this change we are potentially doing less tests with dm-writeboost, so we may experience regressions due to not enough testing. However, also Debian is skipping this test in their infrastructure (see https://ci.debian.net/packages/d/dm-writeboost/unstable/amd64/) and for this module having just a build test should be reasonable enough, so that we can save a lot of I/O bandwidth when testing kernels and dkms.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: dm-writeboost-dkms 2.2.16-0.1
ProcVersionSignature: User Name 6.2.0-1004.4-gcp 6.2.2
Uname: Linux 6.2.0-1004-gcp x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230319
CloudSubPlatform: config-disk (/dev/vdb)
Date: Mon Mar 27 15:03:35 2023
PackageArchitecture: all
SourcePackage: dm-writeboost
UpgradeStatus: No upgrade log present (probably fresh install)

[Andrea Righi (arighi)]

debdiff in attach allows to skip dm-writeboost autopkgtest in small systems.