On Fri, Mar 20, 2020 at 6:55 AM Arnaldo Carvalho de Melo <arnaldo.melo@xxxxxxxxx> wrote: > > Em Thu, Mar 19, 2020 at 04:24:55PM -0700, Andrii Nakryiko escreveu: > > # Why does this matter? > > > > - It’s all about confidence when making BPF changes and about > > maintaining user trust. Automated, repeatable testing on **every** > > change to libbpf is crucial for allowing BPF developers to move fast > > and iterate quickly, while ensuring there is no inadvertent breakage > > of BPF applications. The more libbpf is integrated into critical > > applications (systemd, iproute2, bpftool, BCC tools, as well as > > multitude of internal apps across private companies), the more > > important this becomes. > > Great news, just adding that at each perf pull request libbpf has been > continually compile tested in most of these containers, for a few years > already, with gcc and clang: > Yep, that variety is great! We've been compile-testing for a while in Github across few architectures (amd64, arm64, s390x, ppc64le), running selftests was necessary to capture issues beyond compilation errors and warnings. Plus a lot of old kernel regressions could be detected only in runtime, which is what motivated this work. [...]
