This new option will generate simple TAP files in the given directory, for each path managed by packetdrill: the given one, except if -s is passed.
The TAP files will be named packetdrill_<basename>.tap, where <basename> is the path of the given directory (or subdirectory with -s), or the filename without the extension if a path has been given.
This is particularly useful because the TAP format is used by other test frameworks linked to the kernel: kselftests, kunit, etc. So a CI can easily parse these files to display results in a board, and track regressions per test.
This new option will generate simple TAP files in the given directory, for each path managed by packetdrill: the given one, except if
-s
is passed.The TAP files will be named
packetdrill_<basename>.tap
, where<basename>
is the path of the given directory (or subdirectory with-s
), or the filename without the extension if a path has been given.This is particularly useful because the TAP format is used by other test frameworks linked to the kernel: kselftests, kunit, etc. So a CI can easily parse these files to display results in a board, and track regressions per test.