On Mon, Sep 14, 2020 at 6:43 PM Andrii Nakryiko <andriin@xxxxxx> wrote:
>
> Move almost 200 tests from test_btf into test_progs framework to be exercised
> regularly. Pretty-printing tests were left alone and renamed into
> test_btf_pprint because they are very slow and were not even executed by
> default with test_btf.
>
> All the test_btf tests that were moved are modeled as proper sub-tests in
> test_progs framework for ease of debugging and reporting.
>
> No functional or behavioral changes were intended, I tried to preserve
> original behavior as close to the original as possible. `test_progs -v` will
> activate "always_log" flag to emit BTF validation log.
>
> Signed-off-by: Andrii Nakryiko <andriin@xxxxxx>
> ---
>
> v1->v2:
> - pretty-print BTF tests were renamed test_btf -> test_btf_pprint, which
> allowed GIT to detect that majority of test_btf code was moved into
> prog_tests/btf.c; so diff is much-much smaller;
>
> tools/testing/selftests/bpf/.gitignore | 2 +-
> .../bpf/{test_btf.c => prog_tests/btf.c} | 1069 +----------------
> tools/testing/selftests/bpf/test_btf_pprint.c | 969 +++++++++++++++
> 3 files changed, 1033 insertions(+), 1007 deletions(-)
> rename tools/testing/selftests/bpf/{test_btf.c => prog_tests/btf.c} (85%)
> create mode 100644 tools/testing/selftests/bpf/test_btf_pprint.c
Looks like I forgot to check in a trivial Makefile change (test_btf ->
test_btf_pprint), but I'll hold off until we decided where
pretty-print BTF tests should live.
[...]
