Package: autopkgtest Version: 5.22 Severity: wishlist Hi,
I'd like to limit certain restrictions to particular architectures. Most prominent example would be flaky, where I'd prefer something like Restrictions: flaky [!amd64] or Restrictions: flaky [ppc64el i386] (i.e. annotating restrictions with a dpkg like arch dependency syntax) over 1) marking the test as flaky on all architectures (if the test fails on "well supported" architectures, it should really fail, but if it fails (sporadically) on "exotic" ones (upstream may consider everything beyond amd64 as exotic), this could be marked as flaky until someone manages to investigate (and fix)) or 2) completely disabling the test for this architecture (having an up-to-date flaky failure test log available may serve as a start for investigation). Some examples: src:nvidia-graphics-drivers-tesla-470 fails to build the kernel module for ppc64el kernels due to transitive gpl symbol usage, an issue that needs to be fixed upstream. That has really surprised me since ppc64el is one of the three architectures supported upstream by nvidia-cuda-toolkit. I only noticed that after fixing dkms and autodep8 to make autopkgtest-pkg-dkms actually build kernel modules. (Manually testing to build non-amd64 nvidia kernel modules in a chroot I last tried a few years ago after someone reported a bug.) src:cub/src:libthrust have their upstream testsuite failing to compile on some architectures where the signedness of char differs from the signedness of char on amd64 ... something I need to verify on the latest upstream release before reporting it upstream. Andreas
