On Fri, Jun 21, 2019 at 9:17 AM Dan Rue <dan.rue@xxxxxxxxxx> wrote: > > On Thu, Jun 20, 2019 at 10:17:04PM -0700, Andrii Nakryiko wrote: > > On Thu, Jun 20, 2019 at 1:08 AM Naresh Kamboju > > <naresh.kamboju@xxxxxxxxxx> wrote: > > > > > > selftests: bpf test_libbpf.sh failed running Linux -next kernel > > > 20190618 and 20190619. > > > > > > Here is the log from x86_64, > > > # selftests bpf test_libbpf.sh > > > bpf: test_libbpf.sh_ # > > > # [0] libbpf BTF is required, but is missing or corrupted. > > > > You need at least clang-9.0.0 (not yet released) to run some of these > > tests successfully, as they rely on Clang's support for > > BTF_KIND_VAR/BTF_KIND_DATASEC. > > Can there be a runtime check for BTF that emits a skip instead of a fail > in such a case? I'm not sure how to do this simply and minimally intrusively. The best I can come up with is setting some envvar from Makefile and checking for that in each inidividual test, which honestly sounds a bit gross. How hard is it for you guys to upgrade compiler used to run these test? > > Thanks, > Dan > > > > > > libbpf: BTF_is # > > > # test_libbpf failed at file test_l4lb.o > > > failed: at_file # > > > # selftests test_libbpf [FAILED] > > > test_libbpf: [FAILED]_ # > > > [FAIL] 29 selftests bpf test_libbpf.sh > > > selftests: bpf_test_libbpf.sh [FAIL] > > > > > > Full test log, > > > https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190619/testrun/781777/log > > > > > > Test results comparison, > > > https://qa-reports.linaro.org/lkft/linux-next-oe/tests/kselftest/bpf_test_libbpf.sh > > > > > > Good linux -next tag: next-20190617 > > > Bad linux -next tag: next-20190618 > > > git branch master > > > git commit 1c6b40509daf5190b1fd2c758649f7df1da4827b > > > git repo > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > > > > > Best regards > > > Naresh Kamboju > > -- > Linaro - Kernel Validation
