test: fix build with ring PMD but no bond PMD
authorBruce Richardson <bruce.richardson@intel.com>
Wed, 27 May 2020 14:57:45 +0000 (15:57 +0100)
committerDavid Marchand <david.marchand@redhat.com>
Wed, 1 Jul 2020 10:00:57 +0000 (12:00 +0200)
commit949c97ae310af049075c8745208e8795b9071d9c
tree94d5a4da27081679cc7b741849c7ce57eb46a00a
parent4b7284a71f64f69a55692a2c2018f5c60c49b226
test: fix build with ring PMD but no bond PMD

If the bonding pmd is disabled, all autotest associated with it should be
disabled. However, some of those tests also depended upon the ring PMD so
were placed in a block depending on that driver - and unfortunately that
driver alone. This caused build failures if the ring PMD was enabled but
the bonding PMD disabled, due to missing header files and driver libs.

This error can be reproduced by configuring DPDK using e.g.

  meson configure -Ddisable_drivers=net/[!r]* build

(which will disable all drivers not starting with "r"), and then building
using ninja.

Fix this by moving all link bonding autotests to the one block and putting
a second conditional check within that block for those also requiring the
ring PMD.

Fixes: 7f6ef1664027 ("test/bonding: allow disabling driver")
Fixes: 207b1c813f39 ("test: fix build without ring PMD")

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
app/test/meson.build