Quentin Monnet 9109d6a4b4 ci: create summary for tests and account for bpftool checks result ... The bpftool checks work as expected when the CI runs, except that they do not set any error status code for the script on error, which means that the failures are lost among the logs and not reported in a clear way to the reviewers. This commit aims at fixing the issue. We could simply exit with a non-zero error status when the bpftool checks, but that would prevent the other tests from running. Instead, we propose to store the result of the bpftool checks in a bash array. This array can later be reused to print a summary of the different groups of tests, at the end of the CI run, to help the reviewers understand where the failure happened without having to manually unfold all the sections on the GitHub interface. Currently, there are only two groups: the bpftool checks and the "VM tests". The latter may later be split into test_maps, test_progs, test_progs-no_alu32, etc. by teaching each of them to append their exit status code to the "exitstatus" file. Fixes: 88649fe655 ("ci: run script to test bpftool types/options sync")		2021-11-18 11:19:36 -08:00
..
managers	Add a test step to produce a minimal binary using libbpf.	2021-08-09 13:54:19 -07:00
vmtest	ci: create summary for tests and account for bpftool checks result	2021-11-18 11:19:36 -08:00