So this looks okay, there are unfortunately a bunch of errors in the tests with v1.0.2 against a 5.15 kernel because the 'egress' hook support was only added in 5.16 (https://git.kernel.org/linus/42df6e1d221dddc0f2acf2be37e68d553ad65f96). This results in the following output in a jammy VM:
96 test files, 69 files passed, 1889 unit tests,
717 error, 0 warning
I'd like to suggest one additional change, adding a `-f` option to the nft-test.py invocation in debian/tests/internaltest-py.sh . From the README in test/py/ that tells the testsuite to carry on testing additional families in case of error. With that change in place, I get the following total results, again in a jammy VM with a 5.15 kernel:
96 test files, 69 files passed, 1889 unit tests,
5776 total executed, 719 error, 0 warning
I have not run this in adt, but running the tests manually doesn't return an error value on exit(), even with 700+ errors, so I'm not sure how the adt test will detect a regression that causes more test cases to error.
So this looks okay, there are unfortunately a bunch of errors in the tests with v1.0.2 against a 5.15 kernel because the 'egress' hook support was only added in 5.16 (https:/ /git.kernel. org/linus/ 42df6e1d221dddc 0f2acf2be37e68d 553ad65f96). This results in the following output in a jammy VM:
96 test files, 69 files passed, 1889 unit tests,
717 error, 0 warning
I'd like to suggest one additional change, adding a `-f` option to the nft-test.py invocation in debian/ tests/internalt est-py. sh . From the README in test/py/ that tells the testsuite to carry on testing additional families in case of error. With that change in place, I get the following total results, again in a jammy VM with a 5.15 kernel:
96 test files, 69 files passed, 1889 unit tests,
5776 total executed, 719 error, 0 warning
I have not run this in adt, but running the tests manually doesn't return an error value on exit(), even with 700+ errors, so I'm not sure how the adt test will detect a regression that causes more test cases to error.