Turns out I wasn't looking closely enough at the autopkgtest logs from my local testing - I was trying to run the tests with the pre-built binary packages and whilst it would indicate the internaltest-py.sh tests were passing, they were actually completely failing without any error indication:
autopkgtest [19:10:18]: test internaltest-py.sh: [-----------------------
The nftables library at 'src/.libs/libnftables.so.1' does not exist. You need to build the project.
autopkgtest [19:10:19]: test internaltest-py.sh: -----------------------]
autopkgtest [19:10:20]: test internaltest-py.sh: - - - - - - - - - - results - - - - - - - - - -
internaltest-py.sh PASS
So I think clearly this is a lot less straightforward than I originally thought and perhaps we shouldn't bother with it at this stage - also since as you say since it doesn't fail the autopkgtest run itself then is there any point trying to enable these tests as we won't be able to use it to easily detect regressions in that case.
Turns out I wasn't looking closely enough at the autopkgtest logs from my local testing - I was trying to run the tests with the pre-built binary packages and whilst it would indicate the internaltest-py.sh tests were passing, they were actually completely failing without any error indication:
autopkgtest [19:10:18]: test internaltest-py.sh: [------ ------- ------- --- libnftables. so.1' does not exist. You need to build the project. ------- ------- --]
The nftables library at 'src/.libs/
autopkgtest [19:10:19]: test internaltest-py.sh: -------
autopkgtest [19:10:20]: test internaltest-py.sh: - - - - - - - - - - results - - - - - - - - - -
internaltest-py.sh PASS
So I think clearly this is a lot less straightforward than I originally thought and perhaps we shouldn't bother with it at this stage - also since as you say since it doesn't fail the autopkgtest run itself then is there any point trying to enable these tests as we won't be able to use it to easily detect regressions in that case.